Client-side scripting - suggestions for markup

Lownds, Tony M RV (tml2@PO13.RV.unisys.com)
Tue, 30 Jul 96 16:24:00 CDT


From: "Lownds, Tony M              RV" <tml2@PO13.RV.unisys.com>
To: www-html <www-html@w3.org>
Subject: Client-side scripting - suggestions for markup
Date: Tue, 30 Jul 96 16:24:00 CDT
Message-Id: <31FE7DF9@rsvl_gw.rsvl.unisys.com>


How about restricting <SCRIPT>..</SCRIPT> to the head section of a   
document, and creating a new tag for inlining script-generated data, with   
the actual script code in an attribute. It wouldn't eliminate the need   
for the <SCRIPT><!-- hack for internal scripts, but for people who do use   
external scripts, the need for <SCRIPT>..</SCRIPT> would go away.

Also, after looking at http://www.w3.org/pub/WWW/TR/WD-script.html (is   
this still considered current?), I noticed that nothing is mentioned   
about what the browser should do when a file of a scripting type is   
loaded from, say, a regular hot-link. The way Netscape does things, after   
it loads the file, it is executed and the "returned value" is used as the   
HTML or text source for the page. I'm not sure specifying that a browser   
should support this if the browser supports <SCRIPT> tags is within the   
scope of the above-mentioned working draft, but having some documented   
and endorsed behavior out there would be nice -- putting HTML into a   
scripting langauge is a lot easier than putting a scripting language into   
HTML. Along the same lines, I didn't see the javascript: URL scheme, used   
by Netscape and Microsoft, documented at   
http://www.w3.org/pub/WWW/Addressing/schemes.html. Is this because the   
data: scheme can do the same thing?

 -Tony Lownds