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:01:11 -0700
Message-ID: <4DDD27C7.70901@inkedblade.net>
To: "Phillips, Addison" <addison@lab126.com>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
On 05/24/2011 11:03 PM, Phillips, Addison wrote:
>>> ---
>>> This is a personal summary meant
>>
>> This is all very interesting, and of course should be taken as feedback for
>> Selectors Level 4, but selector matching is completely out-of-scope for CSS
>> Namespaces, which is the topic currently at hand.
>>
>
> Fair enough, although I note that this is the *second* note on this topic and you replied to the earlier one as well.
>
> 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.

~fantasai
Received on Wednesday, 25 May 2011 16:01:44 GMT

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