Feature Request: Add preference to set default section of debugger to be opened on breakpoint
Reported by
b...@encompasscorporation.com,
Oct 5 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.41 Safari/537.36 Steps to reproduce the problem: 1. Set a breakpoint 2. When the breakpoint is reached the source tab is displayed 3. The debugger panel opens the 'Call Stack' section What is the expected behavior? The debugger panel opens a user preferred section. e.g. I want to open the 'Scope' section by default. What went wrong? I rarely refer to the Call Stack when debugging but am generally more interested in the Scope. On each breakpoint I need to scroll and open the Scope when can be tedious. Did this work before? N/A Chrome version: 54.0.2840.41 Channel: beta OS Version: OS X 10.12.0 Flash Version: Shockwave Flash 23.0 r0
,
Oct 7 2016
,
Oct 11 2016
,
Oct 13 2016
,
Oct 13 2016
So, would this be a manual configuration? E.g. you open Settings, each pane has a radio box, and you enable the ones that you want to open by default. Or would DevTools just persist whatever's currently open across sessions?
,
Oct 13 2016
Personally, either option works. However, persisting the current state is more convenient that a manual configuration.
,
Jan 5 2017
Would love for this to be escalated to priority 1. For some reason this incredibly annoying change of always opening the call stack on each breakpoint or even debugger step through/over, even when it has been minimised, was added to chrome within the last 3-4 months. I'm tempted to lodge this as a bug as it is seriously detracts from the user experience and makes it harder & more tedious to debug sources
,
Oct 16 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ligim...@chromium.org
, Oct 5 2016Status: Untriaged (was: Unconfirmed)