Status

Other Applications
DOM Inspector
--
enhancement
11 years ago
6 years ago

People

(Reporter: surkov, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Comment 1

11 years ago
(In reply to comment #0)
> The discussion is available on
> http://groups.google.com/group/mozilla.dev.apps.dom-inspector/browse_thread/thread/980b59c1ea300420/6ceb1217b18062d2#6ceb1217b18062d2
> 

Here it was proposed to import EventSpy extension (https://addons.mozilla.org/en-US/firefox/addon/1100) code in DOMi. It won't be a problem to move its code into DOMi but I can see two things I'm not sure I like.

1. Events are shown in separate dialog. I think it's not correct way for DOMi. I would rather to expose new view for the right panel of DOMi for this. I think it goes much more with DOMi approach. For example, if I select DOM node in DOM view (left panel) then I can choose DOMEvents view in right panel and watch there events occured on that node.

2. Event list and event properties shoudn't be shown in the same tree. I'd use two trees. If I select an item of event list in the first tree then I can inspect event properties in another tree.

Also, I can see the following improvments we should made.

1. UI issue. List of events that can be watched is too small.
2. It should be possible to specify event name to watch because often custom bindings uses own events.
3. It should be possible to specify a phase of event to watch (bubling, capturing, target)
4. It should be possible to see event listeners registered for certain event (it may be another bug).
Severity: normal → enhancement
Duplicate of this bug: 347718
(Reporter)

Comment 3

6 years ago
I think it must be nice to integrate it with Accessible Events view renaming it to Events view (extra tab for DOM event listeners, a11y events aren't turned on by default). It's quite useful to see DOM and a11y events in the same view since it gives you a good idea about event sequences.
Blocks: 388202
You need to log in before you can comment on or make changes to this bug.