1452996 - Emit console warning for script tags with version parameters (rather than just silently ignore them)

Status: NEW

(Core :: DOM: Core & HTML, defect, P3)

Description

[Tom Tromey :tromey]

I had a web site that did:

<script src="blah.js" type="text/javascript;version=1.7"></script>

This worked fine at some point, but when I updated to 59.0 (I think),
it stopped working.  The fix was to remove the ";version=1.7".

Having it not work is fine; however, this changed silently.
It would have been simpler to debug if the failure had been logged
to the console.

Comment 1

[Andrew McCreight [:mccr8]]

Possibly a regression from bug 1417844? That landed in 59 and affected how we deal with JS versions...

Comment 2

[Tom S]

This was actually caused by bug 1428745. I think from some telemetry I looked at before, versioned JS usage was basically non-existent, because the code would not execute in other browsers.

Comment 3

[Kohei Yoshino]

It’s documented here: https://www.fxsitecompat.com/en-CA/docs/2018/script-with-version-parameter-will-no-longer-be-loaded/

Comment 4

[Tom Tromey :tromey]

(In reply to Kohei Yoshino [:kohei] from comment #3)
> It’s documented here:
> https://www.fxsitecompat.com/en-CA/docs/2018/script-with-version-parameter-
> will-no-longer-be-loaded/

One idea for handling this would be to emit a warning with a [Learn more] link to that URL.

Comment 5

[Mike Taylor [:miketaylr]]

(In reply to Tom Tromey :tromey from comment #4)
> (In reply to Kohei Yoshino [:kohei] from comment #3)
> > It’s documented here:
> > https://www.fxsitecompat.com/en-CA/docs/2018/script-with-version-parameter-
> > will-no-longer-be-loaded/
> 
> One idea for handling this would be to emit a warning with a [Learn more]
> link to that URL.

That sounds sensible. Moving to Core::Dom, not sure if that's the right place for this kind of feature request.