Open
Bug 1571907
Opened 6 years ago
Updated 2 months ago
Ensure that DOM mutation breakpoints persist/rebind across refreshes
Categories
(DevTools :: Debugger, enhancement, P3)
DevTools
Debugger
Tracking
(Not tracked)
NEW
People
(Reporter: loganfsmyth, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [debugger-reserve])
Once we've landed basic support for DOM mutation bp state being shared across panels, we can start implementing logic in the toolbox to persist the user's selections and try to re-apply them when new pages appear.
|
||
Updated•6 years ago
|
Whiteboard: [debugger-reserve]
|
||
Updated•6 years ago
|
|
|
||
Updated•6 years ago
|
Whiteboard: [debugger-reserve]
|
|
||
Updated•5 years ago
|
Whiteboard: [debugger-reserve]
|
||
Comment 1•5 years ago
|
||
After placing DOM Mutation Breakpoint in Debugger and refreshing the page, the breakpoint is gone in FF 75.
status-firefox75:
--- → affected
|
|
||
Comment 2•5 years ago
|
||
We are tracking this as an enhancement, as restoring DOM breakpoints requires exploring some heuristics that need to be tweaked. It is missing right now across all versions of Firefox.
status-firefox75:
affected → ---
|
|
||
Comment 3•5 years ago
|
||
Is the heuristics exploration plan written down somehwere?
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Updated•2 months ago
|
Blocks: devtools-webcompat-team
You need to log in
before you can comment on or make changes to this bug.
Description
•