Closed
Bug 1226637
Opened 9 years ago
Closed 6 years ago
[inspector panel] Allow to disable or remove events
Categories
(DevTools :: Inspector, enhancement, P3)
DevTools
Inspector
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1492497
People
(Reporter: fayolle-florent, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: parity-chrome, Whiteboard: [btpp-backlog][todo-mr][t1])
Attachments
(1 file)
29.97 KB,
image/png
|
Details |
Firebug 2.0 allows to disable events in its "Events" panel (see screenshot). A user of Firebug 3.0 misses the feature here, and probably others will: https://github.com/firebug/firebug.next/issues/394 Florent
Reporter | ||
Updated•9 years ago
|
Blocks: firebug-gaps
Please also consider adding it in the side panel, in a tab named Events for the ease of use, as it was on FB 2.0, as requested here https://bugzilla.mozilla.org/show_bug.cgi?id=1226640
Comment 2•8 years ago
|
||
Triaging (filter on CLIMBING SHOES).
Priority: -- → P3
Whiteboard: [btpp-backlog]
Comment 3•8 years ago
|
||
As a point of comparison, Chromium has a "Remove" button next to its list of listeners. :smaug mentioned on IRC that permanently removing a listener can be implemented in devtools without platform changes (while temporarily disabling a listener would likely require platform changes). I'd be happy with just being able to permanently disable them as an initial feature (you can reload the page to get it back if necessary).
Disable and remove are both completely possible so we should add both buttons.
Summary: [inspector panel] Allow to disable events → [inspector panel] Allow to disable or remove events
Whiteboard: [btpp-backlog] → [btpp-backlog][todo-mr][t1]
Updated•7 years ago
|
Severity: normal → enhancement
Comment 8•6 years ago
|
||
Copying over a relevant comment from bug 1449233 by :bgrins: ==== That would be pretty nice! A few thoughts: 1) I think it'd need some UX work as far as how to show disabled event listeners in the inspector / debugger. 2) There's event listener breakpoint work planned at https://github.com/devtools-html/debugger.html/issues/4750 / https://docs.google.com/document/d/1DXzoa7cUZJ_z41_QK1I1nPtyexkgGxup7C_at1SCcQs/edit. It's not the same usecase but maybe we could re-use some of the UI concepts for listing and managing listeners. 3) Would be interesting if it could be extended to any EventTarget when we allow event inspection in the console. ====
See Also: → 1419089
Updated•6 years ago
|
Keywords: parity-chrome
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•