Issue metadata
Sign in to add a comment
|
DevTools call stack sections should be closed
Reported by
l...@insight-rx.com,
Nov 1 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36 Steps to reproduce the problem: 1. Open a webpage and dev tools in chrome 2. Put a breakpoint in any JS code 3. Everytime a breakpoint is hit , call stack section gets expanded, pushing all other relevant debugging info down. What is the expected behavior? Call Stack section should be closed by default. If needed users can open it. When it opens every time a breakpoint is hit , it pushes down all other relevant info and I have to keep closing the call stack. I need the variable values alot more frequently then call stack What went wrong? Makes it an unproductive debugging Did this work before? Yes I don't know the version, but would say it wasn't the case in the last version . This started happening just recently Chrome version: 54.0.2840.71 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 23.0 r0
,
Nov 2 2016
,
Nov 11 2016
,
Nov 30 2016
22 stars on dupe Issue 656109 please merge. see solution in comment #7
,
Nov 30 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by woxxom@gmail.com
, Nov 1 2016