Breakpoints in Fennec's browser.js are ignored
Categories
(DevTools :: Debugger, defect, P2)
Tracking
(firefox65 unaffected, firefox66 unaffected, firefox67 fixed)
Tracking | Status | |
---|---|---|
firefox65 | --- | unaffected |
firefox66 | --- | unaffected |
firefox67 | --- | fixed |
People
(Reporter: JanH, Unassigned)
References
Details
(Keywords: regression)
STR:
Install a current Fennec Nightly and enable USB debugging.
Connect with WebIDE, open the debugger, open chrome://content/browser.js
If WebIDE remembered your last session, clear any pre-existing breakpoints.
Set a new breakpoint anywhere in browser.js, e.g. on the first line of onLocationChange.
Navigate to any page.
Expected:
The breakpoint is hit.
Actual:
Nothing happens. If however you terminate the current debugging session (leave the breakpoint intact!) and then start a new session (for some other reason you might need to re-toggle the debugging switch in Fennec to get it to reappear in WebIDE), the automatically restored breakpoint will be working fine. Any freshly added breakpoints in browser.js on the other hand still don't work. Disabling and then re-enabling the restored breakpoint will cause it to stop working likewise.
Breakpoints added in other files (e.g. jar://components/SessionStore.js) on the other hand work normally.
Mozregression points to https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9b872b266b2ed7aabac64d2f6ccc394277dbaaf3&tochange=266c1eee61a85d63b69b60793365c37a95af2570, i.e. bug 1518661.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
I'm thinking that this could potentially be the same issue as https://bugzilla.mozilla.org/show_bug.cgi?id=1528654, so before I dig into this too much I'd like to land the fix for that and have you check again on the next nightly.
Reporter | ||
Comment 2•5 years ago
|
||
Certainly, will try it.
Comment 3•5 years ago
|
||
The fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1528654 should be in Nightly 67.0a1 2019-02-22 if you're able to test that out.
Reporter | ||
Comment 4•5 years ago
|
||
Yes, seems to work again now.
Comment 5•5 years ago
|
||
Perfect!
Updated•5 years ago
|
Description
•