New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 619861 link

Starred by 1 user
Status: Fixed
Owner:
█ kozyatinskiy@chromium.org
Last visit > 30 days ago
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Disabling JS source maps in Chrome Settings does not work

Reported by jeromin....@gmail.com, Jun 14 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2763.0 Safari/537.36

Steps to reproduce the problem:
1. Load a website with a Source Map file (Typescript in my case)
2. Debugging in typescript works nice when activating JS source maps in chrome settings
3. Disable JS Source Maps in Chrome Setting

What is the expected behavior?
I should be able to add breakpoints in .js file.

What went wrong?
Adding a breakpoint with the mouse opens the corresponding TS file and adds a breakpoint there. I am not able to debug the plain JS.

Did this work before? N/A 

Chrome version: 53.0.2763.0  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0

Comment 1 by jeromin....@gmail.com, Jun 14 2016 

Further testing shows that disabling source maps works, but a reload of the webpage is required. 
We should at least have a reminder to reload the active page.

Comment 2 by pfeldman@chromium.org, Jun 20 2016

Components: Platform>DevTools>JavaScript
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by kozyatinskiy@chromium.org, Oct 4 2017

Status: Fixed (was: Assigned)
Thanks for report.
This one should be fixed, I can not reproduce it in latest Canary.
►

Sign in to add a comment