Closed
Bug 1362439
Opened 7 years ago
Closed 5 years ago
Cannot remove breakpoint set after last valid JavaScript statement
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: account-mozilla-bugzilla, Unassigned)
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20170418123106 Steps to reproduce: 1. Open attached example.html in Firefox 53.0 or Firefox Developer Edition 54.0a2 (both affected, new and old debugger!). 2. Open Developer Tools, go to Debugger. 3. Reload to enable breakpoint sliding. 3. Set breakpoints and directly remove them again in line 7, 8, 10, and 11. Actual results: - Breakpoint in line 7 slides to line 8. Can be removed by clicking on line 8 (expected, correct) - Breakpoints in line 8 and 10 stay there and can be removed by clicking the line again (expected, correct) - Breakpoint in line 11 stays in that line. Can neither be removed by clicking on the gutter nor clicking on the "x" in the Breakpoints pane. Expected results: - Breakpoint in line 11 should either a) not be set at all (since there is no valid statement following that it could slide to) b) be removable. - Note: Breakpoint in line 12 can be removed again, but I don't know why.
Reporter | ||
Updated•7 years ago
|
Component: Untriaged → Developer Tools: Debugger
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Possibly related: "Cannot remove breakpoint when it's set at non-script area" (https://bugzilla.mozilla.org/show_bug.cgi?id=1333219). Although in the other bug a breakpoint is set at a non-script area, not inside the script past the last statement. Can someone reproduce this bug with nightly (where Bug 1333219 is apparently fixed)?
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 4•5 years ago
|
||
I have a similar issue in the newest Firefox Developer Edition (68 b3)
Comment 5•5 years ago
|
||
This is fixed as of https://bugzilla.mozilla.org/show_bug.cgi?id=breakpoint-specificity
@piotrpalek That does not seem to be the same issue, so I would recommend filing that separately.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Flags: needinfo?(odvarko)
You need to log in
before you can comment on or make changes to this bug.
Description
•