Stepping through js with sourcemaps leaves the sourcemaps behind and uses the original code
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Not tracked)
People
(Reporter: lucian303, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
238.27 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:77.0) Gecko/20100101 Firefox/77.0
Steps to reproduce:
Now that sourcemaps are somewhat working again:
Place breakpoint in sourcemapped source.
Step through a few times.
Actual results:
The debugger switches to the original, non sourcemapped source which is not highlighted and is just a giant file. See screenshot. It switches to vendor.js instead of staying in the original file (tab next to it).
Expected results:
Keep stepping through the sourcemapped source code.
Comment 3•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 4•4 years ago
|
||
Forwarding to the devtools component to be investigated.
Comment 5•4 years ago
|
||
Would you be able to create a reproducible example? Sourcemap issues are extremely hard to diagnose without an example unfortunately since they vary so much depending on the particular build process or tooling.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 6•2 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE
.
For more information, please visit auto_nag documentation.
Description
•