Closed
Bug 1576219
Opened 5 years ago
Closed 5 years ago
DOM Mutation Breakpoints: Enable by default
Categories
(DevTools :: Debugger, task)
DevTools
Debugger
Tracking
(firefox70 fixed)
RESOLVED
FIXED
Firefox 70
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: davidwalsh, Assigned: davidwalsh)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete, Whiteboard: [debugger-reserve])
Attachments
(1 file)
This bug tracks turning on DOM Mutation Breakpoints.
|
||
Updated•5 years ago
|
Blocks: dbg-dom-bps
|
Assignee | |
Comment 1•5 years ago
|
||
|
|
Assignee | |
Updated•5 years ago
|
Assignee: nobody → dwalsh
|
||
Updated•5 years ago
|
Keywords: dev-doc-needed
|
||
Updated•5 years ago
|
Pushed by dwalsh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/546362252de1 Enable DOM Mutation Breakpoints r=jlast
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70
|
||
Comment 4•5 years ago
|
||
Created new page Break on DOM mutation and added it to the list of "how to" pages on the Debugger landing page.
Keywords: dev-doc-needed → dev-doc-complete
|
||
Comment 5•5 years ago
|
||
Thank you Irene. Looks really good and detailed. One nit that I noticed would be to maybe expand the 3 choices a bit and mention examples for what kind of APIs or types of changes trigger them
|
|
||
Comment 6•5 years ago
|
||
I've explained them in more detail now and also added example functions and property changes that trigger those breakpoints.
While trying them out I realized that in some cases they are not triggered and in others the breakpoints are unexpectedly removed. I'll file individual bugs for them.
Sebastian
You need to log in
before you can comment on or make changes to this bug.
Description
•