W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2011

Re: I18N-ACTION-40: CSS Selectors and Normalization (new response)

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 25 May 2011 09:26:50 -0700
Message-ID: <4DDD2DCA.3080105@inkedblade.net>
To: "Phillips, Addison" <addison@lab126.com>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
On 05/25/2011 09:13 AM, Phillips, Addison wrote:
>>>
>>> That said, the Namespaces problem and the Selectors problem are
>>> similar problems (from opposite sides). As a result, we can either:
>>
>> Actually, they have one major difference: Namespaces do not interact with
>> anything outside CSS. Their matching is entirely internal to CSS, so problems
>> involving normalization of the source markup or the DOM do not apply.
>>
>
> The matching is entirely internal to CSS, so a stronger normalization
> requirement could be applied to matching (if we were so inclined).
> However, I don't believe that this really alters the recommendation
> as given. Or are you suggesting that namespace prefixes ought to require
> a specific normalization form (in order to be valid)?

It might make sense to require CSS identifiers to parsed into a particular
normalization form, and exposed to the DOM in that form.

~fantasai
Received on Wednesday, 25 May 2011 16:27:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 May 2011 16:27:21 GMT