- From: Aryeh Gregor <Simetrical+w3c@gmail.com>
- Date: Wed, 25 Feb 2009 06:30:51 -0500
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Bert Bos <bert@w3.org>, Yves Lafon <ylafon@w3.org>, www-style@w3.org
On Tue, Feb 24, 2009 at 9:30 PM, Anne van Kesteren <annevk@opera.com> wrote: > On Wed, 25 Feb 2009 05:05:14 +0900, Aryeh Gregor <Simetrical+w3c@gmail.com> > wrote: >> id="112233" and id="-2bar" are actually totally valid IDs in HTML5, as >> far as I can tell: >> >> http://dev.w3.org/html5/spec/Overview.html#the-id-attribute >> >> So I'd think CSS should definitely allow those unescaped, unless >> there's a reason I'm missing to require the escaping. (Clearly it >> does need to impose stricter requirements than HTML5 imposes, like not >> allowing ambiguous characters such as "." or ">" unescaped.) > > You can still select those IDs with CSS. You just need to use escapes. Yes, as I said. But is there any good reason to require the escapes in cases like "112233" where there could be no possible ambiguity?
Received on Wednesday, 25 February 2009 11:31:28 UTC