Debugger panel should be auto-selected when JS execution is paused
Categories
(DevTools :: Debugger, defect)
Tracking
(Fission Milestone:M8, firefox91 fixed)
Tracking | Status | |
---|---|---|
firefox91 | --- | fixed |
People
(Reporter: Honza, Assigned: ochameau)
References
Details
(Whiteboard: dt-fission-m3-mvp)
Attachments
(6 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Debugger pauses at an exception but the panel isn't automatically selected and the panel tab icons isn't highlighted
I have these prefs on:
- fission.autostart
- devtools.target-switching.server.enabled (when retesting later, it feels that this pref has no impact)
STRs:
- Load http://janodvarko.cz/tests/fission/case11/index.html
- Open Debugger, check
Pause on exceptions
- Select the Network panel
- Reload the page
- The Debugger is paused (as well as the page load), but the Debugger panel isn't auto selected.
ER:
The Debugger panel is selected and the panel's icon highlighted, i.e. green (so, the user sees that JS execution is paused).
STR for expected result
- Load http://softwareishard.com/tests/fission/case1/index.html
- Create BP in index.js
- Select the Network panel
- Click
this same page
link twice (to navigate to different domain and back) - Debugger panel hits the BP and is selected
Honza
Assignee | ||
Comment 1•3 years ago
|
||
I do reproduce. I also reproduce the second STR.
Note that it seems to be related to the target into which we hit a breakpoint.
The second STR also fails if you set the BP in the remote target instead of the top document.
Assignee | ||
Comment 2•3 years ago
|
||
I also confirm that devtools.target-switching.server.enabled
has no impact on these failures.
So we probably have some missing test coverage around BP in iframes, or at least toolbox highlight as the debugger seems to be functional other than the highlight.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Also tweak the unselected-pause test to start using Toolbox.isHighlighted
instead of using class internals on multiple layers.
Assignee | ||
Comment 4•3 years ago
|
||
So that test can use this helper instead of querying toolbox internals
Assignee | ||
Comment 5•3 years ago
|
||
This was really confusing.
This test wasn't using the expected "dbg" object. It has to be created
via createDebuggerContext.
Then, it was also confusing that waitForPaused was using an empty waitForLoadedScopes.
So that the browser toolbox test was doing much less assertions.
Last but not least, the test was selecting the debugger before triggering the debugger statement,
this completely defeat the purpose of this test!
Assignee | ||
Comment 6•3 years ago
|
||
Only the second task should be failing without this patch queue.
Also fix a nit in browser_dbg-breaking-from-console.js,
which was one of the rare test covering debugger auto-select.
I'm wondering if I should remove this old test in favor of the new one?
Or meld it into the new one, by covering debugger statements from the console?
Assignee | ||
Comment 7•3 years ago
|
||
Assignee | ||
Comment 8•3 years ago
|
||
Also ensure to close the browser toolbox when the test failed.
Otherwise, it fails with a timeout when trying to re-run the test
which will connect to the old defunct browser toolbox.
Updated•3 years ago
|
Comment 10•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d6827a0e26d0
https://hg.mozilla.org/mozilla-central/rev/7b08c04ad4db
https://hg.mozilla.org/mozilla-central/rev/27b0d76318c5
https://hg.mozilla.org/mozilla-central/rev/250d739d4ff2
https://hg.mozilla.org/mozilla-central/rev/687af8b0bc00
Description
•