W3C home > Mailing lists > Public > www-html@w3.org > January 2003

Re: Recommended Processing model for NOSCRIPT element

From: David Woolley <david@djwhome.demon.co.uk>
Date: Thu, 30 Jan 2003 07:27:11 +0000 (GMT)
Message-Id: <200301300727.h0U7RBi01319@djwhome.demon.co.uk>
To: www-html@w3.org

>     <noscript>
>      JavaScript is not supported!!!

This is an abuse of <noscript> and has no place in an example.  As such,
I think it reflects a false premise in the rest of the text.  (<noscript>
should provide alternative implementations of the function, not complain
about the users configuration.)

I would say that it was bad design practice to mix scripting languages.
If one wants to provide an ECMAScript fallback for VBScript coding
(I'm not sure why, as the object model is common to all scripting
languages, and is the cause of the security concerns, and ECMAScript
is a de facto lowest common denominator), what one needs is an extension
to the object models to allow the scripts to detect the presence of the
other language.

I would say the only sensible clarification would be to require 
<noscript> to only take effect if all scripting options are unavailable.
Received on Thursday, 30 January 2003 02:49:26 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 30 April 2020 16:20:48 UTC