W3C home > Mailing lists > Public > www-style@w3.org > February 2009

Re: Issue in CSS21 grammar?

From: Andrey Mikhalev <amikhal@abisoft.spb.ru>
Date: Wed, 25 Feb 2009 18:56:27 +0300 (MSK)
To: Aryeh Gregor <Simetrical+w3c@gmail.com>
cc: Anne van Kesteren <annevk@opera.com>, Bert Bos <bert@w3.org>, Yves Lafon <ylafon@w3.org>, www-style@w3.org
Message-ID: <Pine.LNX.4.63.0902251847120.7663@master.abisoft.spb.ru>
On Wed, 25 Feb 2009, Aryeh Gregor 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?
>

how about these reasons:
http://www.w3.org/TR/html401/types.html#type-id
http://www.w3.org/TR/REC-xml/#id

if good enough, you have to use css escapes or fix html5 spec ;)

>
>
Received on Wednesday, 25 February 2009 15:57:11 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:16 GMT