Issue metadata
Sign in to add a comment
|
Debugger won't step through formatted code
Reported by
willdema...@gmail.com,
Apr 28 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.29 Safari/537.36 Steps to reproduce the problem: 1. Visit any site with minified JS (e.g. https://www.google.com/chrome/) 2. Select the script in the debugger, such as as "apis.google.com > js > plusone.js" 3. Click 'pretty print {}' button 4. Set breakpoint on an executable line. 5. Refresh the page What is the expected behavior? The debugger should work in the formatted code. The formatted code should be the default pane after refreshing the page. What went wrong? The breakpoint is hit in minified code. Further attempts to pretty-print and step-over cause the view to return to minified code. Did this work before? Yes Chrome 50.0.2661.86 Chrome version: 51.0.2704.29 Channel: beta OS Version: Flash Version: Shockwave Flash 21.0 r0
,
Apr 29 2016
Issue 607702 has been merged into this issue.
,
May 11 2016
Seems like a dupe of bug 415406
,
Aug 26 2016
It has the same root - we discard pretty printed version on reload, but we probably shouldn't. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by allada@chromium.org
, Apr 28 2016