W3C home > Mailing lists > Public > www-style@w3.org > July 2015

Re: [css-page] Editorial issues regarding @page descriptors

From: Lea Verou <lea@verou.me>
Date: Tue, 7 Jul 2015 15:15:41 -0400
Cc: Peter Moulder <pjrm@mail.internode.on.net>, www-style list <www-style@w3.org>
Message-Id: <768F4127-D824-4BA8-A747-879E36E0A779@verou.me>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

> On Jul 6, 2015, at 17:50, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> 
> Inheritance is defined over elements in the element tree.  If @page or
> the @margin rules inherit from an element, or vice versa, then they're
> in the element tree as well.  Like I said, at that point the
> page/margin boxes effectively become pseudo-elements that just have a
> weird at-rule-based syntax for legacy reasons.
> 
> Where they go in the tree is ???.
> 
> ~TJ

I do see inheritance and treating (some of?) them as properties as valuable in this case, as ideally one would want to be able to nest regular CSS rules inside @page rules, to specify styling for the fragments of elements matching the selector that happen to fall on a page that matches the @page rule. Currently it’s a severe limitation that publishers cannot style element fragments based on whether they fall on a left or a right page (for example), and this would provide an elegant and straightforward solution. There are of course the usual parsing issues with nesting, but these could be solved by prepending every such rule with a &. But this is getting a bit off topic for an editorial discussion…

~Lea
Received on Tuesday, 7 July 2015 19:15:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:18 UTC