W3C home > Mailing lists > Public > www-style@w3.org > April 2010

[css3-page] Stability of sections of Paged Media

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 7 Apr 2010 09:51:31 -0700
Message-ID: <p2qdd0fbad1004070951tec1d1e0du773590e31f10e408@mail.gmail.com>
To: www-style list <www-style@w3.org>
Hey all, Chrome Team is planning on implementing some Paged Media
features for use in a few projects.  Most of their uses can be
addressed by simply implementing what CSS2.1 has to say, but there are
two specific cases where that's not adequate, and I'm not completely
sure on what I should tell them to do.

First, they want to be able to control the page size.  This is allowed
through the 'size' property on @page rules in the Paged Media spec.
Right now they're fine with just using a single size of page
throughout the document.  Is it cool to just refer them to Paged Media
for this, then?  Is it legitimate to, for now, go with the rule in the
spec that says implementations can ignore changes to the size of the
page area (caused either by changed in 'size' or 'margin' on @page)
and just use the page area defined for the first page if they want?

Second, they want to be able to clear out the browser decorations that
get automatically put into the margin areas.  Right now, the only way
I see to do that is to use the margin areas from Paged Media and
explicitly set their content to none.  That is, have a setup like

@page {
  @top-left-corner { content: none; }
  @top-left { content: none; }
  @top-center { content: none; }
  @top-right { content: none; }
  ... repeat 12 more times ...

This is because, theoretically, the printing information is specified
in precisely that form in the UA style sheet.

Is this the best way to do this?  Can we come up with an easier way to
clear out all the margins?  If not, is this section stable enough to
implement in Chrome so they *can* use this technique to clear all the
browser's decorations out?

Received on Wednesday, 7 April 2010 16:52:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:44 UTC