Breakpoints section in debugger un-collapses itself when using resume/step in/step out/step return
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Not tracked)
People
(Reporter: tgiles, Unassigned, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(1 file)
425.55 KB,
image/gif
|
Details |
So while debugging the form autofill component, I've set a lot of breakpoints. Most of the time I don't want to see all of these breakpoints so I collapse the breakpoints section/pane in the toolbox. However whenever I step in/over/return/resume the debugger, the breakpoints section reopens itself and takes up valuable real estate I was using for variables/call stack/etc.
This behavior doesn't seem to occur with the Threads section, haven't checked the other sections like Watch expression, XHR breakpoints, etc.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Thank you for the report!
I can easily reproduce the issue on my machine (Fx Nightly, Win 10).
STR:
- Load http://janodvarko.cz/firebug/tests/601/Issue601.htm
- Open the Debugger panel and create BP on line 35
- Click the POST button on the page to hit the BP
- Collapse the BP side panel
- Step, the BP side panel is auto expanded => BUG
Honza
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Hi,
This seems to be a conscious choice, if we are paused due to breakpoint hit, we expand the breakpoints automatically.
How do we want to handle the other case where breakpoints are not intentionally hidden and a breakpoint is hit?
Comment 3•3 years ago
•
|
||
Hi Anshul,
(In reply to Anshul Malik from comment #2)
Hi,
This seems to be a conscious choice, if we are paused due to breakpoint hit, we expand the breakpoints automatically.
How do we want to handle the other case where breakpoints are not intentionally hidden and a breakpoint is hit?
I think this scenario particularly relates to step in/out/over, resume. The breakpoint list pane is ok to open when we hit a breakpoint,
but if it's closed by the user, it should not reopen on stepping or resuming as it's likely more obstructing than useful.
Comment 4•3 years ago
|
||
(bomsy provided the answer, clearing the ni)
Comment 5•3 years ago
|
||
Hello,
I want to work on this issue. Could you please assign me?
Comment 6•3 years ago
•
|
||
Sure. Thanks for the interest.
Assigning to you.
Let me know if you have any questions or clarifications.
Comment 7•3 years ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.
Comment 8•2 years ago
|
||
This has been fixed by Bug 1696157
Comment 9•2 years ago
|
||
Yes i can confirm this is fixed! Thanks Like
Description
•