Skip to content

Commit aeabe48

Browse files
committed
spec/page-view: [Printing generated pages]
1 parent c09236c commit aeabe48

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

spec/page-view.txt

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -420,6 +420,9 @@ Selection of paged content for printing may have to be implemented directly in U
420420

421421
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).
422422

423+
===Proposal===
424+
* 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.
425+
* 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.
423426
====== Issues ======
424427
* 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?
425428
* Media queries for paged view/columns/regions?

0 commit comments

Comments
 (0)