Changeset 248587 in webkit
- Timestamp:
- Aug 12, 2019 8:50:40 PM (5 years ago)
- Location:
- trunk/Source/WebInspectorUI
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebInspectorUI/ChangeLog
r248539 r248587 1 2019-08-12 Devin Rousso <drousso@apple.com> 2 3 Web Inspector: REGRESSION: DOMDebugger: breakpoints are forcibly enabled when resolving DOM breakpoints for newly added nodes 4 https://bugs.webkit.org/show_bug.cgi?id=200639 5 6 Reviewed by Joseph Pecoraro. 7 8 Since DOM breakpoints revolve around a given DOM node, we attempt to restore DOM breakpoints 9 whenever new nodes are added by matching them to the path of the DOM breakpoint. When doing 10 so, we should be in a "temporarily restoring breakpoints" mode so that we don't forcibly 11 enable all breakpoints. 12 13 * UserInterface/Controllers/DOMDebuggerManager.js: 14 (WI.DOMDebuggerManager.prototype._speculativelyResolveDOMBreakpointsForURL): 15 (WI.DOMDebuggerManager.prototype._nodeInserted): 16 1 17 2019-08-12 Devin Rousso <drousso@apple.com> 2 18 -
trunk/Source/WebInspectorUI/UserInterface/Controllers/DOMDebuggerManager.js
r248201 r248587 562 562 } 563 563 564 if (nodeIdentifier) 565 this._resolveDOMBreakpoint(breakpoint, nodeIdentifier); 564 if (!nodeIdentifier) 565 return; 566 567 this._restoringBreakpoints = true; 568 this._resolveDOMBreakpoint(breakpoint, nodeIdentifier); 569 this._restoringBreakpoints = false; 566 570 }); 567 571 } … … 827 831 continue; 828 832 833 this._restoringBreakpoints = true; 829 834 this._resolveDOMBreakpoint(breakpoint, node.id); 835 this._restoringBreakpoints = false; 830 836 } 831 837 }
Note: See TracChangeset
for help on using the changeset viewer.