breakpoints and call stacks not using source map
Reported by
ghost...@gmail.com,
Apr 5 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3053.3 Safari/537.36 Steps to reproduce the problem: 1. Go to a web page that uses a source map 2. Open dev tools 3. Cause an exception What is the expected behavior? Dev tools shows the execution point in the original js file and shows the original function names in the call stack What went wrong? Dev tools shows the execution point in the obfuscated js file and obfuscated function names in the call stack. You can see from the attached picture that it says "Source Map detected", the folders from the source map are being displayed in the tree, however the minified code is shown Did this work before? N/A Chrome version: 59.0.3053.3 Channel: dev OS Version: 10.0 Flash Version: There are no errors in the console. The minified js file has //# sourceMappingURL=source.map at the end and source.map has the correct /directory/filename.js paths in it. It's detecting and understanding the source map correctly because the un-minified directories and files appear in the source tree (and they're orange instead if blue) but both the call stack and breakpoints use the minified js instead of the un-minified ones.
,
Apr 6 2017
,
Apr 6 2017
,
Dec 6 2017
Won't fix due to lack of feedback. |
||||
►
Sign in to add a comment |
||||
Comment 1 by allada@chromium.org
, Apr 5 2017