W3C home > Mailing lists > Public > public-html@w3.org > May 2007

Re: 'role' should be property

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Wed, 23 May 2007 14:23:13 +0100
Message-ID: <640dd5060705230623q4f1276f1t61724702a666f4b8@mail.gmail.com>
To: "Philip Taylor (Webmaster)" <P.Taylor@rhul.ac.uk>
Cc: public-html@w3.org

Hi Philip,

On 23/05/07, Philip Taylor (Webmaster) <P.Taylor@rhul.ac.uk> wrote:
>
>
>
> Mark Birbeck wrote:
>
> > So, say we make all div's blue:
> >
> >  div { background-color: blue; }
> >
> > We've done two things; the first is to define a rule that creates a
> > collection of elements,
>
> No.  The collection was pre-existing.  Had you chosen to
> write "div.whatever {background-color: blue} then I would
> have agreed with you, but not using the code you cite.

I'll try to clarify what I was getting at, since the key point is not
what selector you use, but that _any_ selector is creating a notional
collection.

A document has all sorts of nodes, at all sorts of different levels of
the hierarchy. The CSS selectors can be seen as creating dynamic
collections of sub-sets of those nodes--"dynamic" because if you add
or remove a node from the DOM, it will be reflected in the 'nodeset'
or 'collection' that the styling is applied to. Since my rule selects
all div's at any level of the hierarchy, then it's creating a notional
collection ready to be operated on.

Regards,

Mark

-- 
  Mark Birbeck, formsPlayer

  mark.birbeck@x-port.net | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.
Received on Wednesday, 23 May 2007 13:23:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:15:58 GMT