W3C home > Mailing lists > Public > public-html@w3.org > August 2009

The script element

From: Geoffrey Sneddon <gsneddon@opera.com>
Date: Mon, 03 Aug 2009 14:01:48 +0200
Message-ID: <4A76D1AC.6000803@opera.com>
To: HTMLWG WG <public-html@w3.org>
> The default, which is used if the [type] attribute is absent, is 
> "text/javascript".

This should be "which is used if the attribute is absent or empty" to
match existing behaviour, and the algorithm below. (Or is this meant to
be part of the conformance requirements for documents? If that's the
case that needs to be clarified.)

> When examining types to determine if they support the language, user
> agents must not ignore unknown MIME parameters  types with unknown
> parameters must be assumed to be unsupported.

What about charset, which is forbidden in conforming documents? Should 
that be treated as unknown? IE, Opera and Chromium don't run scripts 
with charset, Firefox does (but Firefox just ignores parameters in general).

> The following lists some MIME types and the languages to which they refer:
> application/ecmascript
> application/javascript
> application/x-ecmascript
> application/x-javascript
> text/ecmascript
> text/javascript
> text/javascript1.0
> text/javascript1.1
> text/javascript1.2
> text/javascript1.3
> text/javascript1.4
> text/javascript1.5
> text/jscript
> text/livescript
> text/x-ecmascript
> text/x-javascript

Off that list, only IE and Chromium support text/javascript1.1, 
text/javascript1.2, and text/javascript1.3, and nothing supports the 
remainder of the text/javascript1.* media types (it appears Firefox and 
Opera don't treat @language as "text/" + @language, with Firefox having 
a separate list for @language, while Opera just ignores @language 

As such, I don't think it's entirely useful to have that list as is, as 
most aren't supported by multiple browsers.

Geoffrey Sneddon  Opera Software
Received on Monday, 3 August 2009 12:02:30 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:49 UTC