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

[Bug 10068] Suggest making noscript obsolete but conforming

From: <bugzilla@jessica.w3.org>
Date: Wed, 07 Jul 2010 14:14:44 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OWVOe-00046w-7L@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10068





--- Comment #9 from Shelley Powers <shelleyp@burningbird.net>  2010-07-07 14:14:43 ---
(In reply to comment #8)
> I think the objection to "deprecated" is that it implies that support will be
> removed in a future version.  Practically speaking, we can't drop support for
> any feature once it's widely used on the web, so this is misleading.  In the
> terminology that HTML5 currently uses, you could ask that noscript be
> non-conforming, or be conforming but raise a validator warning.  "Obsolete but
> conforming" is a subset of the latter, and isn't necessarily what you want (is
> it really obsolete, or we just think it's a bad idea?).

I believe another bug was opened on the deprecated versus obsolete but
conforming terminology. Is there any way you can add your comment to that bug?
I'd like to reply to your comment, but I don't want to confuse the purpose of
this bug by tangential (but important) discussions on another concern about the
HTML5 spec.

-- 
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 14:14:47 UTC

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