Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
spec:page-view [2012/02/19 20:15] – [Proposals] bkemperspec:page-view [2014/12/09 15:48] (current) – external edit 127.0.0.1
Line 404: 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 'overflow:paged'. For example:
 +
 +<code>
 +article h1 { page-break-before: always; page: chapter-start-page; }
 +</code>
 +
 +The above code starts a new page whenever there is an H1, and then uses the @page named "chapter-start-page" as its template.
 +
 +Even without considering regions and @slot, the "chapter-start-page" could have a different font-size, color, number of columns, column-rules, page area, etc., while the other declarations for H1 could make it like a header, with its own background, height, :after and/or :before pseudo-elements, etc., to help give the page a unique design. With @slot, it could also have other css-3 regions flows in it, and additional content elements.
 ===== 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 411: 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 'overflow:paged' in a way similar to iframes: providing UI to print just that one element, but defaulting to print it along with the entire root page. If printing just the overflow:paged element, its position within its parent or ancestors is ignored, and the upper left corner of the element will go in the upper left corner of the printable area of the paper. Right-clicking on an element should also present an option to print any of the ancestors that have 'overflow:paged' on them.
 +  * the '.print()' function of 'window' should be extended to also be used on any element, so that document.getElementById("myPagedView").print() would work to print that one element. Then authors can include a button to print their paged element.
 ====== Issues ====== ====== Issues ======
   * Paged view doesn't automatically mean "paged media" (which is commonly used as "for printing" and can't be repurposed). Should there be a way to declare that a paginating viewer (e.g. iframe) needs to render the same visuals as what would be printed?   * Paged view doesn't automatically mean "paged media" (which is commonly used as "for printing" and can't be repurposed). Should there be a way to declare that a paginating viewer (e.g. iframe) needs to render the same visuals as what would be printed?
   * Media queries for paged view/columns/regions?   * Media queries for paged view/columns/regions?
 
spec/page-view.1329711330.txt.gz · Last modified: 2014/12/09 15:48 (external edit)
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki