[Bug 10068] Suggest making noscript obsolete but conforming

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10068





--- Comment #22 from Lee Kowalkowski <lee.kowalkowski@googlemail.com>  2010-07-08 07:59:48 ---
(In reply to comment #14)
> I agree it is a crude method, but it is a method that is used. In these
> environments, trusted scripts are allowed through the proxy, so not only is the
> browser capable of scripting, it is used to execute trusted scripts. The
> content of the noscript element is only rendered when a browser cannot execute
> scripts, so is not seen in these environments. The scenario can be avoided when
> authors avoid noscript and use progressive enhancement instead.

Because a scenario can be avoided, doesn't mean the HTML author is obliged to. 
If perfect progressive enhancement was commonplace, there'd be no need for such
proxies to trust any scripts, because the scripts would not be necessary.  

The issue in this scenario still isn't noscript, it's poor proxying.  The lack
of visible fallback content isn't a big enough deal to redesign, after all, the
organisations adopting such proxies can still close their browser windows, or
print their documents, and probably shouldn't be playing games whilst at work.

-- 
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 Thursday, 8 July 2010 07:59:51 UTC