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 UTC