Closed
Bug 1539509
Opened 6 years ago
Closed 6 years ago
Ensure consistent breakpoint syncing behavior
Categories
(DevTools :: Debugger, enhancement, P2)
DevTools
Debugger
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1540848
People
(Reporter: bhackett1024, Assigned: bhackett1024)
References
(Blocks 1 open bug)
Details
As described in bug 1537589, depending on the order in which sources are loaded we can end up in a situation where a pending breakpoint ends up creating two breakpoints after reloading, if the source has since been edited. The behavior here should be consistent regardless of evaluation order, and only one breakpoint should be installed. As part of this, it would also be good to tighten up the breakpoint syncing code and express it entirely in terms of other actions --- addBreakpoint and removeBreakpoint --- instead of having it be its own action which reducers need to process separately. This will reduce the surface of action/client operations which need to be kept in sync by bug 1539506.
Updated•6 years ago
|
Priority: -- → P2
Assignee | ||
Comment 2•6 years ago
|
||
Yeah, bug 1540848 took care of this.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(bhackett1024)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•