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

Re: Issue in CSS21 grammar?

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 25 Feb 2009 11:30:42 +0900
To: "Aryeh Gregor" <Simetrical+w3c@gmail.com>, "Bert Bos" <bert@w3.org>
Cc: "Yves Lafon" <ylafon@w3.org>, www-style@w3.org
Message-ID: <op.upvykx0d64w2qv@annevk-t60.oslo.opera.com>
On Wed, 25 Feb 2009 05:05:14 +0900, Aryeh Gregor  
<Simetrical+w3c@gmail.com> wrote:
> On Tue, Feb 24, 2009 at 2:56 PM, Bert Bos <bert@w3.org> wrote:
>> Why should UAs reject "#-2bar"? It is just extra work. Especially if you
>> consider the following rule:
>>
>>    #112233, p { color: #112233 }
>>
>> which the UA would have to reject, because the first HASH tokens is used
>> in the role of an ID.
>
> 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.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Wednesday, 25 February 2009 02:31:32 GMT

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