W3C home > Mailing lists > Public > www-style@w3.org > June 2007

Re: [css3-selectors] Namespace name lookup mechanisms

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 29 Jun 2007 15:06:44 +0200
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org
Message-ID: <lh0a83hkuhemu2ipbhunvpcstu1j62k30u@hive.bjoern.hoehrmann.de>

* fantasai wrote:
>If there are multiple mechanisms, then the namespace prefix declared by
>a given mechanism is case-sensitive or case-insensitive as defined by that
>mechanism. If a case-sensitive mechanism declares FOO and a case-insensitive
>mechanism declares foo, then foo can only match the second declaration, and
>FOO will match the first or the second depending on which mechanism takes
>precedence, which is outside the scope of the Selectors spec since it does
>not specify a namespace declaration mechanism. Basically, a case-insensitive
>declaration declares all case variants of the prefix.

The text with the changes you announced would be "The case sensitivity
of namespace prefixes in selectors is defined by the mechanism used to
declare them".

  Mechanism A: Namespace prefixes in selectors are case-sensitive.
  Mechanism B: Namespace prefixes in selectors are case-insensitive.

This is a conflict. You are avoiding the problem by speaking of the
case-sensitivity of the mechanism, while the draft text speaks of the
case-sensitivity of the prefix in the selector.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Friday, 29 June 2007 13:08:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:29 UTC