Closed Bug 1005825 Opened 10 years ago Closed 5 years ago

Add "break on mutate" support in the inspector (breakpoint on DOM modification)

Categories

(DevTools :: Inspector, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1547692

People

(Reporter: pbro, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [difficulty=hard] )

With bug 1004678 fixed, we'll be able to add "break on mutation" options to the inspector's markup-view.
Bug 1004678 is about making this possible at debugger level, and this bug should be about 2 things:

- adding the necessary UI to the markup-view (firebug does this within the context menu that appears when right-clicking on a node, see https://dl.dropboxusercontent.com/u/714210/firebug-break-on-mutation.png),
- starting the debugger in the background when a "break on mutation" option is chosen, and switching to the debugger panel in the toolbox when the code is paused.
Depends on: dbg-dom-bps
Regarding the additional UI in the markup view, it would be nice if the element that had this state applied had some visual indication beyond a checked item in the context menu.  Maybe a small icon next to the item in the tree, or some kind of border to call out elements with the behavior active.
(In reply to Brian Grinstead [:bgrins] from comment #1)
> Regarding the additional UI in the markup view, it would be nice if the
> element that had this state applied had some visual indication beyond a
> checked item in the context menu.  Maybe a small icon next to the item in
> the tree, or some kind of border to call out elements with the behavior
> active.

Another idea for the UI would be to show a breakpoint icon next to the element in the markup view, same as the icon you see when clicking in a gutter on script in the debugger
(Enhancing summary because I couldn't find this bug earlier..)
Summary: Add "break on mutate" support in the inspector → Add "break on mutate" support in the inspector (breakpoint on DOM modification)
Assigning P1 priority for some devedition-40 bugs. 

Filter on '148DD49E-D162-440B-AE28-E22632FC20AC'
Priority: -- → P1
Whiteboard: [devedition-40] → [devedition-40][difficulty=hard]
Whiteboard: [devedition-40][difficulty=hard] → [difficulty=hard]
Filter on CLIMBING SHOES
Priority: P1 → P3
Product: Firefox → DevTools
Severity: normal → enhancement

Work has been started and will be tracked in bug 1547692.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
No longer blocks: devtools-webcompat-team
You need to log in before you can comment on or make changes to this bug.