Skip to content

Commit c09236c

Browse files
committed
spec/page-view: [Column breaks and page breaks in regions]
1 parent ef87d88 commit c09236c

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

spec/page-view.txt

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -403,6 +403,16 @@ If "page" is an element or pseudo-element generated from template and rendered i
403403
**Proposal:**
404404
//TODO. Named breaks have been discussed, add a specific proposal here//
405405

406+
===[css3-page]===
407+
[css3-page] already has this feature, we just need to make sure that it applies to 'overflow:paged'. For example:
408+
409+
<code>
410+
article h1 { page-break-before: always; page: chapter-start-page; }
411+
</code>
412+
413+
The above code starts a new page whenever there is an H1, and then uses the @page named "chapter-start-page" as its template.
414+
415+
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.
406416
===== Printing generated pages =====
407417
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.
408418

0 commit comments

Comments
 (0)