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 20:06] – [Proposals] bkemper | spec:page-view [2012/02/19 20:15] – [Proposals] 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 325: | Line 325: | ||
| * event **regionLayoutUpdate** to inform about dynamic content change | * event **regionLayoutUpdate** to inform about dynamic content change | ||
| Which is enough for generating pages this way | Which is enough for generating pages this way | ||
| + | |||
| + | ===[css3-regions] with [css3-page]=== | ||
| + | See previous section about combining css3-page @page with regions and a new @slot feature. Then imagine different variations of that sample code embedded in different media queries. @page provides named @page rules that act as templates, and media queries would let you use different @page rules and templates for varying orientations and screen sizes. | ||
| ===IDPF page templates proposal=== | ===IDPF page templates proposal=== | ||