New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 661293 link

Starred by 6 users

Issue metadata

Status: Duplicate
Merged: issue 656109
Owner:
Last visit > 30 days ago
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

DevTools call stack sections should be closed

Reported by l...@insight-rx.com, Nov 1 2016

Issue description

UserAgent: 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
 

Comment 1 by woxxom@gmail.com, Nov 1 2016

Bisect: 411262 (good) - 411270 (bad) released as 54.0.2827.0
https://chromium.googlesource.com/chromium/src/+log/62c31132..6f10f638?pretty=fuller
Suspecting https://crrev.com/2234193002 as the only devtools related change, moreover it actually does add a line of code that expands the Stack panel unconditionally.
Components: -UI Platform>DevTools
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: sureshkumari@chromium.org
 Issue 664121  has been merged into this issue.
22 stars on dupe  Issue 656109 

please merge. see solution in comment #7


Mergedinto: 656109
Status: Duplicate (was: Assigned)

Sign in to add a comment