Issue metadata
Sign in to add a comment
|
Call stack is auto-expanding stepping through code
Reported by
mitchell...@sencha.com,
Oct 14 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36 Steps to reproduce the problem: 1. Hit a breakpoint 2. Collapse call stack panel (in Sources) 3. Step through code What is the expected behavior? The call stack panel should remain collapsed as you step through code. What went wrong? The call stack panel expands each time you step through code (does not matter if step into, step out or step over). Did this work before? Yes 53 Chrome version: 54.0.2840.59 Channel: beta OS Version: OS X 10.12.0 Flash Version: Shockwave Flash 23.0 r0 Sometimes the call stack is very long making inspecting the local variables and the watch panel go out of view when that is an important piece to observe as you step through code.
,
Oct 18 2016
Please fix!
,
Oct 18 2016
Also, it's about 2000px wide!
,
Oct 21 2016
,
Oct 31 2016
This makes debugging a terrible experience. Please fix. Thank you!
,
Nov 18 2016
If this is somehow difficult to fix, is there a way we move the stack block down below the Scope block for the time being?
,
Nov 21 2016
Comment #7 - That makes even more sense since there's related information on Watch and Scope. Would vote for that if I could.
,
Nov 30 2016
user reporting as still issue and also found these as dupe tickets: 656109, 664121, 661293
,
Nov 30 2016
comment #1 from Issue 661293 : 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.
,
Nov 30 2016
Issue 661293 has been merged into this issue.
,
Nov 30 2016
,
Dec 1 2016
Same here. Any ETA on fix? This makes devtools super uncomfortable to use. Also, maybe Scope should be above Call stack, imho it's more useful that way (you'd be able to see both at least some of the time).
,
Dec 1 2016
Is this just being ignored? I work with this daily and it's made debugging the worst part of my day.
,
Dec 1 2016
#14 - if you want a quick fix, you can always inspect the Developer Tools (press F12, undock, press Control + Shift + J) and add a temporary CSS rule that hides the call stack.
,
Dec 2 2016
,
Dec 2 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7f30067e0b27a6e3899cc57b6f92dfac5215479e commit 7f30067e0b27a6e3899cc57b6f92dfac5215479e Author: kozyatinskiy <kozyatinskiy@chromium.org> Date: Fri Dec 02 03:05:43 2016 [DevTools] Don't expand CallStackSidebarPane on pause if it was collapsed BUG= 656109 R=lushnikov@chromium.org Review-Url: https://codereview.chromium.org/2544193002 Cr-Commit-Position: refs/heads/master@{#435839} [modify] https://crrev.com/7f30067e0b27a6e3899cc57b6f92dfac5215479e/third_party/WebKit/Source/devtools/front_end/sources/CallStackSidebarPane.js
,
Dec 2 2016
ETA: fix will be available in Canary tomorrow.
,
Dec 3 2016
Your change meets the bar and is auto-approved for M56 (branch: 2924)
,
Dec 3 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/33b6a683ebb0ac3ea188bf5244f2cd6616babf9a commit 33b6a683ebb0ac3ea188bf5244f2cd6616babf9a Author: Alexey Kozyatinskiy <kozyatinskiy@chromium.org> Date: Sat Dec 03 18:01:34 2016 [DevTools] Don't expand CallStackSidebarPane on pause if it was collapsed BUG= 656109 R=lushnikov@chromium.org Review-Url: https://codereview.chromium.org/2544193002 Cr-Commit-Position: refs/heads/master@{#435839} (cherry picked from commit 7f30067e0b27a6e3899cc57b6f92dfac5215479e) Review URL: https://codereview.chromium.org/2552553002 . Cr-Commit-Position: refs/branch-heads/2924@{#317} Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059} [modify] https://crrev.com/33b6a683ebb0ac3ea188bf5244f2cd6616babf9a/third_party/WebKit/Source/devtools/front_end/sources/CallStackSidebarPane.js
,
Jan 18 2017
Issue 677539 has been merged into this issue.
,
Jan 26 2017
,
Sep 18 2017
I'm still experiencing this issue in Chrome 62 and Chrome 63 on Ubuntu. @kozyatin said on dec 02 2016: > ETA: fix will be available in Canary tomorrow. should this be in mainline today? Only in Chromium? What version? @phistuck said on dec 01 2016: > you can always inspect the Developer Tools (press F12, undock, press Control + Shift + J) and add a temporary CSS rule that hides the call stack. How would you do that quickly? Without expanding 10 divs? There are no ids on them.
,
Sep 18 2017
For anyone googling: The lack of ids makes you need to manually inspect the location of the specific part. This works for me, but you might have to edit this.
When opening the inspector on a breakpoint, and that annoying intrusive stack won't stay away, enter this:
1. Ctrl + Shift + J - Open devtools' devtools
2. Esc - Open console
3. document.querySelector('.widget.vbox.insertion-point-sidebar .vbox').querySelectorAll('.vbox')[3].style.display = 'none';
Hope that saves someone 10 minutes.
,
Sep 23 2017
Also experiencing this on Chrome 61 for mac
,
Sep 24 2017
#23, #25 - please, file a new issue for it. You can comment here with the new issue number so you do not create two new issues.
,
Sep 25 2017
New issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=768257
,
Sep 25 2017
I'm not sure there are different developer tools in Chromium because some seem to have the problem and others don't, but there was also a new and/or related bug here: Issue 766086
,
Aug 21
This is still an issue as of August 2018
,
Aug 22
#29 - please, file a new issue with details such as -
- What are you debugging (Node? Or a Chrome tab)?
- If you are debugging Node, how do you open the Developer Tools ("Open dedicated DevTools for Node" on chrome://inspect? Somehow else?)
- What platform are you using?
- What is your Chrome version?
You can comment here with the new issue number.
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by caseq@chromium.org
, Oct 17 2016Labels: -OS-Mac OS-All
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)