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: Phillips, Addison <addison@lab126.com>
Date: Wed, 25 May 2011 09:13:57 -0700
To: fantasai <fantasai.lists@inkedblade.net>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <131F80DEA635F044946897AFDA9AC3476A931F0346@EX-SEA31-D.ant.amazon.com>
> >
> > 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)?

Received on Wednesday, 25 May 2011 16:14:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:07 UTC