W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: [css3-values] viewport units (vw/vh/vmin/vmax) and @page rules

From: Håkon Wium Lie <howcome@opera.com>
Date: Mon, 25 Feb 2013 00:39:58 +0100
Message-ID: <20778.42190.985427.945049@gargle.gargle.HOWL>
To: Simon Sapin <simon.sapin@kozea.fr>
Cc: www-style@w3.org
Also sprach Simon Sapin:

 > >   > * Viewport units in the page context (but maybe not inside margin
 > >   > at-rules) refer to the UA’s default page size, ignoring any stylesheet.
 > >   >
 > >   > * Viewport units are based not on the first page, but on an hypothetical
 > >   > page that does not match any page name or page pseudo-
 > >   > class. (In other words, only consider @page rules without a page selector.)
 > >   >
 > >   > * That hypothetical page does not inherit from the root element.
 > >   > Alternative: @page never inherits from the root.
 > >   >
 > >   > Would that work?
 > >
 > > Yes, it seems to make sense.
 > >
 > > I'd like for @page to inherit from the root element, to avoid having
 > > to set font family, size etc.
 > 
 > Yes, I’d like to preserve that use case too. But it’s really tricky to 
 > keep that and still avoid having a viewport unit depend on itself.
 > 
 > One way maybe is to cut inheritance only for the purpose of determining 
 > viewport units, but that seems slippery.

I think it's ok. It's better than having lots of error situations, or
having to set lots of declarations. The general principle should be
that the root provides any information it can provide, and the
mythical ur-page provides the rest.

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Sunday, 24 February 2013 23:40:33 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:06 GMT