please support sourceMappingURL=file:///C:/foo/bar/baz.js.map
Reported by
jeromin....@gmail.com,
Mar 31 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 OPR/35.0.2066.92 Steps to reproduce the problem: 1. generate JS from Typescript with the last line //# sourceMappingURL=file:///C:/foo/bar/baz.js.map 2. copy JS file on a webserver, but do not upload the source map 3. try to debug it What is the expected behavior? chrome dev tools should fetch the source map even if this is a local file. What went wrong? If i copy the source map to the server, the dev tools finds the original files JS on http has: //# sourceMappingURL=baz.js.map map on http has: "sources":["file:///C:/foo/bar/baz.ts"... But if the source map is not on the server it does not work: JS on http has: //# sourceMappingURL=file:///C:/foo/bar/baz.js.map map on disc is the same: "sources":["file:///C:/foo/bar/baz.ts"... Did this work before? N/A Chrome version: 48.0.2564.116 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Apr 4 2016
,
Apr 4 2016
No, i did not. It is not needed for the working version (source map on server) either.
,
Apr 4 2016
IMHO adding folder to the workspace is to show the devTools where the files are. But this information is in this case already provided in the JS file with the sourceMappingURL.
,
Aug 4 2016
Due to the security model, DevTools cannot just freely access your filesystem. By adding folder to the chrome devtools, you explicitly grant permission to read/write contents of the folder. |
|||
►
Sign in to add a comment |
|||
Comment 1 by lushnikov@chromium.org
, Apr 4 2016Status: Assigned (was: Unconfirmed)