Randy Webb wrote:
Johannes Baagoe said the following on 9/5/2007 5:20 PM:
>Randy Webb :
>>You forgot to mention that the type attribute is obsolete though.
I sure learn a lot here! Since when is that the case?
I shouldn't have said the type attribute was obsolete, it isn't. What
is obsolete is the only acceptable value for the attribute.
text/javascript was obsoleted the minute it was standardized.
Wrong. RFC4329, which you are you are referring to is *not* on the IETF
Standards Track. In fact, its status section explicitly states that "It
does not define an Internet standard of any kind."
That it was registered at IANA by initiative of the IESG/IETF as being
obsolete due to the presumption of the latter or the RFC's author (or him
not being clear enough on the subject, let alone not having demonstrated
sufficient experience in the field of application of the said media type
to date) has no bearing for (at least) my recommendation regarding that,
as using that so-called obsolete media type is the best current practice
due to the maximum possible support of it among current and possibly future
user agents. Much in contrast to the alternatives defined by that RFC.
The explanation for "obsolete" given to me by the RFC's author, Bjoern
Hoermann, in de.comp.lang.javascript was that according to RFC4288, the only
alternatives would have been "common" and "limited use", while the former
was strongly objected and the latter was seen as not being heavily endorsed
by the participants of the respective discussion.[1] Which IMHO would beg
the question whether any of those people has ever written a cross-browser
client-side script in an ECMAScript implementation.
http://pointedears.de/scripts/test/mime-types/
PointedEars
___________
[1] <b1********************************@hive.bjoern.ho ehrmann.de>
--
"Use any version of Microsoft Frontpage to create your site. (This won't
prevent people from viewing your source, but no one will want to steal it.)"
-- from <http://www.vortex-webdesign.com/help/hidesource.htm>
