On Jul 6, 2:40 pm, Yan Huang <[email protected]> wrote:
> Hi,
>
> I constantly find all types of weirdness while working with the
> monitorEvents() API. For example, it seems not able to capture events whose
> target is the body tag.
You could post a test case to the issues list:
http://code.google.com/p/fbug/issues/list
> Another thing I am uncertain about is, how this events monitoring utility
> relates to the DOM level two 3-phase event propagation model?
FIrebug just adds another listener and prints into the Console when it
fires.
Third, is this
> monitorEvents API useful to identify
> all JS function handlers registered for a given event?
Not as far as I know. We need the new Firefox api for this. Supporting
event listener analysis one of my top priorities for 1.5.
jjb
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
