22.12.2013 Views

W3C CSS2 Cascading Style Sheets, level 2 - instructional media + ...

W3C CSS2 Cascading Style Sheets, level 2 - instructional media + ...

W3C CSS2 Cascading Style Sheets, level 2 - instructional media + ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

’always’, ’left’, and ’right’ take precedence over ’avoid’. See the section on<br />

allowed page breaks [p. 183] for the exact rules on how these properties may<br />

force or suppress a page break.<br />

13.3.2 Using named pages: ’page’<br />

’page’<br />

Value: | auto<br />

Initial: auto<br />

Applies to: block-<strong>level</strong> elements<br />

Inherited: yes<br />

Percentages: N/A<br />

Media: visual, paged<br />

The ’page’ property can be used to specify a particular type of page where an<br />

element should be displayed.<br />

Example(s):<br />

This example will put all tables on a right-hand side landscape page (named<br />

"rotated"):<br />

@page rotated {size: landscape}<br />

TABLE {page: rotated; page-break-before: right}<br />

The ’page’ property works as follows: If a block box with inline content has a<br />

’page’ property that is different from the preceding block box with inline content,<br />

then one or two page breaks are inserted between them, and the boxes after the<br />

break are rendered on a page box of the named type. See "Forced page breaks"<br />

below. [p. 184]<br />

Example(s):<br />

In this example, the two tables are rendered on landscape pages (indeed, on<br />

the same page, if they fit), and the page type "narrow" is not used at all, despite<br />

having been set on the DIV:<br />

@page narrow {size: 9cm 18cm}<br />

@page rotated {size: landscape}<br />

DIV {page: narrow}<br />

TABLE {page: rotated}<br />

with this document::<br />

<br />

...<br />

...<br />

<br />

13.3.3 Breaks inside elements: ’orphans’, ’widows’<br />

’orphans’<br />

182

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!