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.

Thank you for the report!

I can easily reproduce the issue on my machine (Fx Nightly, Win 10).

STR:

1. Load http://janodvarko.cz/firebug/tests/601/Issue601.htm
2. Open the Debugger panel and create BP on line 35
3. Click the POST button on the page to hit the BP
4. Collapse the BP side panel
5. Step, the BP side panel is auto expanded => BUG

Honza

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?

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.

(bomsy provided the answer, clearing the ni)

Hello,

I want to work on this issue. Could you please assign me?

Sure. Thanks for the interest.
Assigning to you.

Let me know if you have any questions or clarifications.

This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.

This has been fixed by Bug 1696157

Yes i can confirm this is fixed! Thanks Like