Paged media

[bertfrees]

Paged Media

The ‘@page’ rule

• Find out how declarations within page and margin contexts cascade: see http://www.w3.org/TR/2013/WD-css3-page-20130314/#cascading-and-page-context.
• Currently @page:first is defined as "matching the first printed page of a volume". However when it follows a page type selector should it instead match the first page of a sequence of pages of the specified type (i.e. similar to the way the volume pseudo-classes are defined), or not?
• Allow combination of page pseudo-classes, e.g. @page:blank:left { ... }.

Using Named Pages: the 'page' property

• Should the forced page break that is introduced when necessary be a page break of type 'always' or 'right'? (Currently "Rules for page breaking" says 'right'.)
• Should I mention class A break points? Saying "Applies to: boxes that create class A break points" is essentially the same as "Applies to: block | list-item".
• Possibly add a section "The 'page' property works as follows..." as in http://www.w3.org/TR/2013/WD-css3-page-20130314/#using-named-pages.

Page Breaking

• Describe how block-level boxes are split if they exceed the boundaries of a page (can also be described in Box Model)
  • When a page break splits a box, the box's margins, borders, and padding have no visual effect where the split occurs.
  • A block-level element that is split over several pages may have a different width on each page.
  • See Box Model for Breaking

Controlling Page Breaks

• Explain differences with original specification: initial value of widows/orphans is 0 instead of 2, the properties are not inherited, etc.

Rules for Page Breaking

• What does class C mean? Is this situation possible in braille CSS? (Answer: I don't think so)

"Between the content edge of a block container box and the outer edges of its child content (margin edges of block-level children or line box edges for inline-level children) if there is a (non-zero) gap between them."

• Add guidelines for optimizing page breaks? See http://www.w3.org/TR/2012/WD-css3-break-20120823/#best-breaks.
• Explain simplifications with respect to original breaking rules [CSS3BREAK]: no block-perpendicular fragmentation, only one break type (what about volume breaks?), no monolithic elements, only normal flow, etc.
• Connection with line breaking and volume breaking rules?
• Implicitly forced page break (caused by 'page' property) could also be of type 'always'.

---

See also

• http://dev.w3.org/csswg/css-page
• http://www.w3.org/TR/2012/WD-css3-break-20120823/#page-break
• http://www.w3.org/TR/2012/WD-css3-break-20120823/#widows-orphans
• http://www.w3.org/TR/2013/WD-css3-page-20130314
• http://www.w3.org/TR/2013/WD-css3-page-20130314/#margin-boxes
• http://www.w3.org/TR/2013/WD-css3-page-20130314/#page-breaks
• http://www.w3.org/TR/2013/WD-css3-page-20130314/#page-selector-and-context
• http://www.w3.org/TR/CSS21/page.html
• http://www.w3.org/TR/CSS21/page.html#break-inside
• http://www.w3.org/TR/CSS21/page.html#page-box
• http://www.w3.org/TR/CSS21/page.html#page-breaks