Would also be fine with "//# sourceMappingURL" without the "=" and the
URL. Can implement this in firefox devtools pretty quickly, just waiting
on ideas to solve the implicit original URL.
On 10/11/13 7:04 AM, John Lenz wrote:
> Is there a reason to add a new annotation rather than simply leaving
> the URL off the existing one?
> On Jul 10, 2013 3:08 PM, "Fitzgerald, Nick" > wrote:
> On 7/9/13 9:25 AM, Michał Gołębiowski wrote:
> Ping again? We keep getting hurt because of that in jQuery,
> e.g. this CDN has a wrong location of the minified file:
> Could we have the `@hasImplicitSourceMapUrl` added to the
> spec, please?
> I'm ok with adding `//# hasImplicitSourceMapURL` although (at the
> risk of bike shedding) I think `//# implicitSourceMap` is a better
> To find the source map for the script you just append ".map" to
> the script's URL?
> For inline scripts in a page do you still just append the ".map"?
> How would this work with http://example.com?
> http://example.com.map doesn't work, would we do
> http://example.com/.map? Disallow implicit source map linking for
> inline scripts? What about eval'd code?
> Can you (or someone else) write up a proposal that answers these
> questions and gives a solid algorithm for finding an implicit
> source map that we would be able to just drop into the spec?
> dev-js-sourcemap mailing list