cannot reliably set/use breakpoints in formatted minified javascript
Reported by
pie...@gmail.com,
Dec 2 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36 Steps to reproduce the problem: 1. navigate to https://www.typescriptlang.org/play/ 2. f12 3. go to file typescriptServices.js 4. Pretty print 5. search for "e.optionDeclarations =" (should be around line 33500) 6. double-click search result to navigate to line in typescriptServices.js 7. attempt to set breakpoint on line "e.optionDeclarations = [{" 8. BUG: breakpoint jumps to 'return' statement in nested 'E(e)' function definition. What is the expected behavior? breakpoint set correctly What went wrong? breakpoints jump around erratically. Did this work before? N/A Chrome version: 54.0.2840.99 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0
,
Dec 9 2016
Able to reproduce this issue on Win-10, Mac 10.12.1 and Ubuntu 14.04 using chrome reported version #54.0.2840.99 and latest canary #57.0.2945.0. This is a non-regression issue as it is observed from M30 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Dec 14 2016
the new inline breakpoints should help out (eventually), but i agree this is pretty frustrating.
,
Jun 19 2017
This bug is reproducible in our workspace (linux ubuntu dev for mobile UC & chrome). The rootcause is in appcache.cc. Since some unkown (for me) version, devtools start sending formatter_worker.js request with both query string and ref string. But even the latest chromium code in appcache.cc doesn't strip out query parts. A simple patch is suggested in attachment. ^_
,
Jun 19 2017
,
Oct 16 2017
,
Dec 7 2017
This one is not pretty print problem. We do not support separate break locations for expression divided by comas. I think we can fix it. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ajha@chromium.org
, Dec 5 2016