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

Re: CSS21] CR-CSS21-20070719, 6.4.3 Selector specificity

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Tue, 18 Sep 2007 18:32:57 +0200
To: Andrei Polushin <polushin@gmail.com>
Cc: www-style@w3.org
Message-ID: <ubuve3hffgdijb91tgnfscfgedbdieiet5@hive.bjoern.hoehrmann.de>

* Andrei Polushin wrote:
>I have to decide how to implement this. First, I see the intent is to have
>multiple pseudo-elements per selector. Second, I have to implement the
>specificity calculation. Then I see two contradictory specifications and
>decide that the wording in [CSS21] takes priority over [CSS3SELECT]. Now you
>tell me that the wording in [CSS21] couldn't be treated as normative.

Specifity is an artifical construct used in the CSS specifications to
define which declarations wins if multiple declarations apply. You do
not have to implement it literally, you just need to get the ordering
right, and the specifications are consistent in defining the ordering.

If, at some point, we allow multiple pseudo-elements in a selector, we
will also define precedence rules for selectors involing more than one
pseudo-element as necessary. We do not know yet how this might look
like, the notes in the specification just serve as a reminder that an
implementation should not be designed in a way that makes supporting
multiple pseudo-elements at the selector level difficult.
-- 
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 Tuesday, 18 September 2007 16:33:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:52 GMT