Eventbug rising
49 views
Skip to first unread message
John J Barton
Sep 18, 2009, 8:06:54 PM9/18/09
to Firebug
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
listeners:
http://blog.getfirebug.com/2009/09/18/eventbug-rising/
jjb
Kevin Decker
Sep 19, 2009, 1:41:26 PM9/19/09
to Firebug
Very cool.
What are the "Allows-Untrusted" captions in reference to?
What are the "Allows-Untrusted" captions in reference to?
johnjbarton
Sep 19, 2009, 1:50:48 PM9/19/09
to Firebug
On Sep 19, 10:41 am, Kevin Decker <kpdec...@gmail.com> wrote:
> Very cool.
>
> What are the "Allows-Untrusted" captions in reference to?
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
jayarjo
Oct 28, 2009, 8:19:50 AM10/28/09
to Firebug
Oh, my...
Can't you just release it as separate FireBug extension? :(
On Sep 19, 9:50 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> On Sep 19, 10:41 am, Kevin Decker <kpdec...@gmail.com> 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/n...
Can't you just release it as separate FireBug extension? :(
On Sep 19, 9:50 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> On Sep 19, 10:41 am, Kevin Decker <kpdec...@gmail.com> 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
Honza (Jan Odvarko)
Oct 28, 2009, 8:28:12 AM10/28/09
to Firebug
> Can't you just release it as separate FireBug extension? :(
It is a separate Firebug extension - EventBug.
Honza
jayarjo
Oct 28, 2009, 8:35:39 AM10/28/09
to Firebug
I meant, can't you make it available as an extension... already? :)
Let it be even alpha. It is not available, right? Or is it?
Honza (Jan Odvarko)
Oct 28, 2009, 9:30:36 AM10/28/09
to Firebug
We are almost ready, the plan is to get something out next week :-)
Honza
Honza
jayarjo
Oct 29, 2009, 1:37:45 AM10/29/09
to Firebug
Wow.
Waiting impatiently :)
Waiting impatiently :)
Honza (Jan Odvarko)
Oct 30, 2009, 8:08:59 AM10/30/09
to Firebug
jayarjo
Oct 31, 2009, 4:41:53 AM10/31/09
to Firebug
That's huge!
jayarjo
Oct 31, 2009, 5:24:02 AM10/31/09
to Firebug
I've got very javascriptized web-site. In fact nothing exist on
initial load and is constructed dynamically later through ajax calls.
When inspecting my dynamically built DOM elements I can see attached
events in EventBug, but when I expand them only "not implemented in
Javascript" is displayed. But it is. Handler is encapsulated inside a
widget, but it exists.
initial load and is constructed dynamically later through ajax calls.
When inspecting my dynamically built DOM elements I can see attached
events in EventBug, but when I expand them only "not implemented in
Javascript" is displayed. But it is. Handler is encapsulated inside a
widget, but it exists.
John J Barton
Oct 31, 2009, 1:59:04 PM10/31/09
to Firebug
On Oct 31, 2:24 am, jayarjo <jaya...@gmail.com> wrote:
> I've got very javascriptized web-site. In fact nothing exist on
> initial load and is constructed dynamically later through ajax calls.
> When inspecting my dynamically built DOM elements I can see attached
> events in EventBug, but when I expand them only "not implemented in
> Javascript" is displayed. But it is. Handler is encapsulated inside a
> widget, but it exists.
If you create a small but complete test case and post it to the issues
list I can take a look.
http://code.google.com/p/fbug/issues/list
jjb
jayarjo
Nov 1, 2009, 1:48:10 AM11/1/09
to Firebug
It's my custom built widget, on top of jQuery UI Widget framework.
I'll try to create a test case.
On Oct 31, 9:59 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
> On Oct 31, 2:24 am, jayarjo <jaya...@gmail.com> wrote:
>
> > I've got very javascriptized web-site. In fact nothing exist on
> > initial load and is constructed dynamically later through ajax calls.
> > When inspecting my dynamically built DOM elements I can see attached
> > events in EventBug, but when I expand them only "not implemented in
> > Javascript" is displayed. But it is. Handler is encapsulated inside a
> > widget, but it exists.
>
> What is a widget?
>
> If you create a small but complete test case and post it to the issues
Reply all
Reply to author
Forward
0 new messages