On Sep 19, 10:41 am, Kevin Decker <[email protected]> wrote:
> Very cool.
>
> What are the "Allows-Untrusted" captions in reference to?

I don't know, here is the answer I got when I asked on the bugzilla
bug:
------
> I don't know what allowsUntrusted or inSystemEventGroup  mean.
Event listeners can be added to listen either all events or only
trusted
events.
User initiated events are trusted and so are events dispatched by
chrome.
By default content event listeners listen all events, chrome listeners
only
trusted.
http://mxr.mozilla.org/mozilla-central/source/dom/public/idl/events/nsIDOMNSEventTarget.idl#51

Gecko has 2 "event groups". Default and system. When event is
dispatched,
event target chain is looped and default listeners are called, then
there is a new loop and listeners in the system event group are
called.
Native default handling happens in the bubble phase of system event
group
(==PostHandleEvent).
-----------

Maybe we should suppress these attributes in web pages, they don't
affect web devs I think.

jjb

>
> On Sep 18, 7:06 pm, John J Barton <[email protected]> wrote:
>
> > Just a peak at some work we are doing to allow Firebug to show event
> > listeners:http://blog.getfirebug.com/2009/09/18/eventbug-rising/
>
> > 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to