This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
spec:page-view [2012/02/19 20:06] – [Proposals] bkemper | spec:page-view [2014/12/09 15:48] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
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=== | ||
Line 401: | Line 404: | ||
//TODO. Named breaks have been discussed, add a specific proposal here// | //TODO. Named breaks have been discussed, add a specific proposal here// | ||
+ | ===[css3-page]=== | ||
+ | [css3-page] already has this feature, we just need to make sure that it applies to ' | ||
+ | |||
+ | < | ||
+ | article h1 { page-break-before: | ||
+ | </ | ||
+ | |||
+ | The above code starts a new page whenever there is an H1, and then uses the @page named " | ||
+ | |||
+ | Even without considering regions and @slot, the " | ||
===== Printing generated pages ===== | ===== Printing generated pages ===== | ||
In many of the page view situation, it is reasonable to expect that user would wish to print the content that is already preseneted in paged manner. They may prefer to either print the exact pages that they see on screen, or re-generate adaptive content for print. Either way, they will be printing content of page view, which may not be the root element of HTML document. | In many of the page view situation, it is reasonable to expect that user would wish to print the content that is already preseneted in paged manner. They may prefer to either print the exact pages that they see on screen, or re-generate adaptive content for print. Either way, they will be printing content of page view, which may not be the root element of HTML document. | ||
Line 408: | Line 421: | ||
Running script before print (to generate a new set of pages for print media) -- may need an event on HTMLDocument (and not sure it is a good idea). | Running script before print (to generate a new set of pages for print media) -- may need an event on HTMLDocument (and not sure it is a good idea). | ||
+ | ===Proposal=== | ||
+ | * UA should treat any object with ' | ||
+ | * the ' | ||
====== Issues ====== | ====== Issues ====== | ||
* Paged view doesn' | * Paged view doesn' | ||
* Media queries for paged view/ | * Media queries for paged view/ |