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

Issue metadata

Status: WontFix
Email to this user bounced
Closed: Oct 2012
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Sign in to add a comment

Issue 133854: Source map data URI does not load original sources

Reported by, Jun 20 2012

Issue description

Chrome Version       : 21.0.1171.0 (Developer Build 141382)
URLs (if applicable) :
Other browsers tested: none

What steps will reproduce the problem?
1. Encode a source map in base64 and include a //@ sourceMappingURL=data:......
2. Open devtools console, look in sources

What is the expected result?
Original source file should show up in the sources tab.

What happens instead?
Original source file shows up in the list of files, but is not fetched (it shows up as an empty file), even though it is present on the server.

Note: The referenced URL was actually part of  Issue 12621 , but this issue involved chrome trying to load the data URI, which was resolved. Unfortunately that test case should now work and still does not. The original source file (which, incidently, should be relative to the document URL according to the source map spec) appears to be empty, although the file is available.

Comment 1 by, Jun 22 2012

Labels: Feature-DevTools

Comment 2 by, Oct 11 2012

Status: Assigned

Comment 3 by, Oct 11 2012

Status: WontFix
Source urls are relative to source map url. In your case source map url is data url, so you need to either provide absolute path or add 'sourceRoot' field to source map.
"sources": ["/source-map-inspector/foo.js"] should work as well.

Comment 4 by, Mar 11 2013

Project Member
Labels: -Area-Undefined -Feature-DevTools Cr-Platform-DevTools

Sign in to add a comment