From:  "Fitzgerald, Nick" <nfitzgerald@mozilla.com>
Date:  12 Oct 2013 00:20:21 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.js-sourcemap
Subject:  

Re: Allow utilizing fragments of the minified file name for map file names

NNTP-Posting-Host:  63.245.216.66

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:
>         http://cdnjs.cloudflare.com/ajax/libs/jquery/2.0.3/jquery.min.js
>         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
>     name.
>
>     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?
>
>     Nick
>     _______________________________________________
>     dev-js-sourcemap mailing list
>     dev-js-sourcemap@lists.mozilla.org
>     
>     https://lists.mozilla.org/listinfo/dev-js-sourcemap
>