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

Re: [css3-page] Stability of sections of Paged Media

From: fantasai <fantasai.lists@inkedblade.net>
Date: Sat, 17 Apr 2010 18:45:17 -0700
Message-ID: <4BCA642D.8000102@inkedblade.net>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: www-style list <www-style@w3.org>, yuzo@google.com, jeffharris@google.com, luizp@google.com, nmvc@google.com, hayato@google.com, hamaji@google.com
On 04/14/2010 04:55 PM, Tab Atkins Jr. wrote:
> Further requests from our internal team!
>
> 1. Concerning section 8.2 of the current Editors Draft, where it talks
> about content overflowing the page area, it currently leaves the
> choice of how to deal with this explicitly undefined, and puts "clip
> the content" as the least preferred option.  Our internal team at
> Chrome actually prefers "clip the content" over all other methods,
> since that most closely matches desktop printing standards.  We'd
> prefer that either that list be reordered with "clip the content" as
> the most preferred option, so that they can have some sort of
> assurance that other browsers would probably act the same, or that
> there be some sort of explicit control over how the UA handles
> overflowing page areas.  At the very least, saying "clip" or "auto",
> with "auto" meaning "do what you want, in this order of priority" (the
> priority list can continue to put "clip" at the end then).

The reason "clip the content" is preferred is because it's assumed
that the user considers access to the content to be most important
thing. I don't think it's accurate to say that current applications
perfer "clip the content". IIRC, many PDF readers rescale content
to fit onto the page sheet if it is designed for a different page
size.

Note that this is talking about page boxes that are sized (with
the 'size' property) to be larger than the page sheet. Content that
overflows the page area is covered in a separate section.

> 2. Can we depend on setting "@page { margin: 0; }" to mean that the
> page area is the entire size of the page?  It's understood that the
> printer itself has device limitations on how close to the paper edge
> it can print, but we'd like to still be able to position things
> directly from the paper edge.  The relevant part is the last paragraph
> of section 7.0, "It is recommended that user agents establish a
> default page margin via the user agent stylesheet that includes any
> non-printable area. It is further recommended  that authors assume
> that the default page area will not include unprintable regions.".
> This only sets the default page margin, but stills allows it to be
> overridden to be smaller than this, and thus to include unprintable
> regions within the page area, correct?

Correct. @page { margin: 0; } is intended to cover the entire page
sheet, and may cause the page area to extend into unprintable regions.

~fantasai
Received on Sunday, 18 April 2010 02:45:37 GMT

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