SCRIPT

MegaZone (megazone@livingston.com)
Mon, 22 Sep 1997 03:39:36 -0700 (PDT)


Message-Id: <199709221039.DAA24553@server.livingston.com>
To: www-html@w3.org
Date: Mon, 22 Sep 1997 03:39:36 -0700 (PDT)
From: MegaZone <megazone@livingston.com>
Subject: SCRIPT

I see a potential problem with the new SCRIPT definition.

'language' has been deprecated in favor of 'type'.   However, my 
understanding of type is that it does not contain version info.

ie - it is always 'text/javascript' and not 'text/javascript1.1' or
'text/javascript1.2'/

This version info is vital to scripting and backwards compatibility.

It is possible to write a very feature rich script in JavaScipt1.2,
a functional but less feature rich script in JavaScript1.1, and say
some dummy routines to prevent errors in JavaScript1.0.

In fact, Netscape themselves encourage this.  Functions all occupy the
same namespace, so you put oldest version first.  And since the UA only
loads scripts when it can support the version, the newer versions of
the functions will replace older version where support is available.

<SCRIPT language="JavaScript1.0">
old script
</SCRIPT>
<SCRIPT language="JavaScript1.1">
newer script
</SCRIPT>
<SCRIPT language="JavaScript1.2">
newest script
</SCRIPT>

Am I mistaken about type's inability to carry version info?

If I'm not, then I would say we either should not deprecate 'language' or
we need a new 'version' attribute to suppliment 'type'.

-MZ
--
Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 4464 Willow Road, Pleasanton, CA 94588