- From: <bugzilla@jessica.w3.org>
- Date: Wed, 07 Jul 2010 15:16:21 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10068 --- Comment #13 from Shelley Powers <shelleyp@burningbird.net> 2010-07-07 15:16:20 --- (In reply to comment #12) > (In reply to comment #7) > > 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. > > This is bad craftsmanship too, such crude proxy servers ought to be handling > noscript elements too. It is not the responsibility of the HTML author to > anticipate and mitigate this scenario. Actually it is, if they're worth being paid. HTML web developers have an obligation to ensure their applications respond gracefully in all situations, including no JavaScript support, or even scripts being stripped. That's the whole purpose behind progressive enhancement. -- 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 15:16:26 UTC