W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2010

[Bug 10068] Deprecate noscript

From: <bugzilla@jessica.w3.org>
Date: Wed, 07 Jul 2010 08:36:43 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OWQ7X-0007Hj-3p@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10068





--- Comment #7 from Gez Lemon <gez.lemon@gmail.com>  2010-07-07 08:36:42 ---
Not only is progressive enhancement a much better technique for dealing with
cases where scripts are not supported in the client, it also caters for the
case where the browser does support scripting, but all scripts are removed by a
proxy server. In some secure environments, such as banks, scripts are removed
from pages by a proxy server. In this scenario, the browser supports scripting,
so the noscript content is not displayed. Not relying on noscript avoids this.

I can't think of a good use case for keeping noscript. I didn't realise that
deprecated was a term to be avoided, but I'm happy with "Obsolete, but
conforming".

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 7 July 2010 08:36:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:51 UTC