Steps to reproduce
Steps to reproduce the problem:
- Create a local directory structure like so:
- Open the js file, and ensure it has a sourceMappingUrl directive, pointing to the map file, but also ensure the url has a leading / like so:
- Serve the directory up (browse the index.html page)
What is the expected behavior?
According to the Sourcemap V3 spec:
When the source mapping URL is not absolute, then it is relative to the generated code’s “source origin”.
If the generated code is associated with a script element and the script element has a “src” attribute, the “src” attribute of the script element will be the source origin.
This means I would expect edge to issue a request for the map file on /foo/bar.js.map
What went wrong?
Using fiddler (requests for source map files don’t appear to show up on the network tab) edge makes a request:
GET /foo.js.map HTTP/1.1
The leading “/” in the sourceMappingUrl appears to make edge treat resolve the url to the map file as relative to the site root rather than the source origin…
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Ibrahim O.”
Changed Assigned To from “Ibrahim O.” to “Jacob R.”
Changed Status to “Confirmed”
Changed Assigned To from “Jacob R.” to “Newton J.”
Changed Assigned To from “Newton J.” to “Jeff F.”