From:  Peter van der Zee <>
Date:  09 May 2013 23:07:49 Hong Kong Time

Re: Change sourceMappingURL comment syntax to avoid IE JS conditional compilation issues


Eddy, can't the browser support both but issue an extra deprecation warning
for using the @ version? As mentioned before there are already many tools
and sources that rely on the @ version. No sense breaking them just like
that. The console warning should help devs migrate to the new spec.

Also, pushing that patch right now, without a new version of the spec at
all, effectively means killing any source maps for firefox :p

- peter

On Thu, May 9, 2013 at 4:24 PM, Eddy Bruel  wrote:

> On 5/9/13 4:00 PM, Micha? Go?e;biowski wrote:
>> It seems Nick Fitzgerald is OK with the change of the `@` symbol to sth
>> different, e.g. `#`. I'd like to ask to introduce such a change to the spec
>> as soon as possible. The reason is the source maps topic is really gaining
>> traction, more & more projects start supporting it and the later we change
>> it the more compatibility baggage we'll have to deal with. Currently the
>> spec is fresh enough it's easy to convince most tools authors to introduce
>> changes to adhere to changes in the spec but it won't be the same further
>> in the future (and I'm afraid at one point it may be so difficult that the
>> no-change option wins here).
>> So, to reiterate - I'd like for the pragma to change really soon, timing
>> is really important here.
>> ______________________________**_________________
>> dev-js-sourcemap mailing list
>> dev-js-sourcemap@lists.** 
> I just filed bug 870361  show_bug.cgi?id=870361>
> with a working patch. All it needs is a review.
> ______________________________**_________________
> dev-js-sourcemap mailing list
> dev-js-sourcemap@lists.**