W3C home > Mailing lists > Public > www-style@w3.org > January 2004

RE: [css3-page] Section 3.4.2. Cascading in the page context

From: BIGELOW,JIM (HP-Boise,ex1) <jim.bigelow@hp.com>
Date: Wed, 14 Jan 2004 10:08:08 -0800
Message-ID: <79417AA297C63F4EA33B68AC105464A9A380C7@xboi22.boise.itc.hp.com>
To: werner.donne@re.be
Cc: www-style@w3.org

Werner, you wrote
> The specificity calculation is expressed in terms of 
> selectors, which in turn are expressed in terms of elements. 
> It could indeed also apply to at-page rules. But shouldn't 
> the specification then say somewhere that an "anonymous" 
> at-page rule corresponds to the universal element selector 
> and a named at-page rule to a type selector?
> 
 Werner, you make a good point. I'm inclined to expand Section 3.4.2.
"Cascading in the page context" to indicate that the properties in the named
page override those in a page. Does this seem reasonable to you?

- Jim

[1] http://www.w3.org/TR/css3-page/#cascading-and-page-context 



> 
> BIGELOW,JIM (HP-Boise,ex1) wrote:
> > Werner,
> > 
> > Thank you for your comment, it has been assign the number 34.
> > 
> > You wrote:
> > 
> >>Shouldn't there also be a cascading relationship between
> >>"anonymous" at-page rules and named at-page rules, where the 
> >>latter would be stronger then the former?
> > 
> > 
> > I think the concept of specificity [1] already supplies the 
> > relationship you describe.
> > [1] Item 3 of 
> http://www.w3.org/TR/CSS21/cascade.html#cas> cading-order
> > 
Received on Wednesday, 14 January 2004 13:08:11 GMT

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