This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
spec:page-view [2012/02/19 18:55] – [Proposal:] bkemper | spec:page-view [2012/02/19 20:09] – [Proposal:] bkemper | ||
---|---|---|---|
Line 53: | Line 53: | ||
Presents content of a separate document in paged view. Can be used to build a page viewer with custom UI. | Presents content of a separate document in paged view. Can be used to build a page viewer with custom UI. | ||
- | ===In addition (Add-On to Proposal): | + | ===In addition... (Add-On to Proposal): |
* **@page** applies to " | * **@page** applies to " | ||
Line 277: | Line 277: | ||
<div class=" | <div class=" | ||
</ | </ | ||
+ | </ | ||
+ | |||
+ | ===[css3-regions] with [css3-page]=== | ||
+ | [css3-page] already has the concept of different pages having boxes of variable content and style depending on their order, and on certain elements triggering different @page layouts: margin boxes. Margin boxes are created by margin at-rules inside the page context. Margin boxes can accept a subset of CSS properties, just as Regions do. So, in the same way that margin boxes are declared using @margin inside different named or pseudo-classed @page rules, other boxes //within// the "page area" would be created using @slot inside different named or pseudo-classed @page rules. Each @slot could have a ' | ||
+ | |||
+ | < | ||
+ | |||
+ | HTML, body { height: | ||
+ | body { overflow: paged; } | ||
+ | @page { | ||
+ | @slot(0) { flow-from: article-flow; | ||
+ | @slot(1) { flow-from: sidebar-flow; | ||
+ | } | ||
+ | @page chapter-start-page { | ||
+ | @slot(0) { flow-from: article-flow; | ||
+ | @slot(Logo) { content: | ||
+ | } | ||
+ | |||
+ | article { flow-into: article-flow; | ||
+ | aside { flow-into: sidebar-flow; | ||
+ | article h1 { page-break-before: | ||
</ | </ | ||
====Ideas==== | ====Ideas==== |