Feature: Stop Auto-opening the Call Stack
Reported by
aneil.ma...@gmail.com,
Feb 4 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: Opening the call stack automatically every time the debugger starts is annoying. Opening the call stack means the Locals aren't visible, so every single time, the developer needs to close the call stack after starting the debugger, which is annoying. For example, see: https://groups.google.com/forum/#!topic/google-chrome-developer-tools/sll_xyjJaSQ Two possible fixes: 1. don't auto-open 2. remember last state 3. move call stack below Locals To reproduce 1. Make file.js with contents "debugger" 2. node file.js --inspect-brk 3. chrome debugger opens with call stack open 4. click the call stack to hide it 5. debug again 6. The call stack view is visible again What is the expected behavior? What went wrong? Call stack always opens when debugger starts Did this work before? N/A Chrome version: 64.0.3282.140 Channel: stable OS Version: OS X 10.13.2 Flash Version:
,
Feb 5 2018
,
Feb 6 2018
,
Oct 9
Seriously, I can't be the only person in the world irritated by this behavior.
,
Dec 5
We need some heuristics in order to fix this. There is no way to strictly distinguish the breakpoint or exception stop from the stepping...
,
Dec 19
I'm unable to reproduce this while stepping. After collapsing the Call Stack manually, stepping preserves the closed state during the entire DevTools session. Are people still able to repro this on Canary? I am able to reproduce in these cases: - closing and reopening DevTools - resizing DevTools to trigger the layout switch between vertical / horizontal (debugger sidebar becomes drawer) In these cases, we entirely forget the closed state, and it seems reasonable to address those, but I'd like to confirm these. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by viswatej...@techmahindra.com
, Feb 5 2018