Closed Bug 1575688 Opened 5 years ago Closed 3 years ago

DOM Mutation Breakpoints should use an nsIMutationObserver or something else instead of deprecated DOM mutation events

Categories

(DevTools :: Debugger, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1694548

People

(Reporter: loganfsmyth, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [debugger-reserve])

We're adding some ugly logic in https://bugzilla.mozilla.org/show_bug.cgi?id=1562708 because we use DOM Mutation events, and we should stop doing that.

While MutationObserver is a no-go because it notifies JS observers on the next microtask checkpoint, there is nothing stopping us from making our own subclass of nsIMutationObserver to allow us to get mutation notifications synchronously while avoiding the deprecated DOM events.

Whiteboard: [debugger-reserve]
Summary: DOM Mutation Breakpoints should use an nsIMutationObserver-based API instead of deprecated DOM mutation events → DOM Mutation Breakpoints should use an nsIMutationObserver or something else instead of deprecated DOM mutation events
Whiteboard: [debugger-mvp]
Whiteboard: [debugger-mvp] → [debugger-reserve]
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.