[ ] Currently @page:first is defined as "matching the first printed page of a volume". However when it follows a page type selector should it instead match the first page of a sequence of pages of the specified type (i.e. similar to the way the volume pseudo-classes are defined), or not?
[ ] Allow combination of page pseudo-classes, e.g. @page:blank:left { ... }.
[ ] Should the forced page break that is introduced when necessary be a page break of type 'always' or 'right'? (Currently "Rules for page breaking" says 'right'.)
[ ] Should I mention class A break points? Saying "Applies to: boxes that create class A break points" is essentially the same as "Applies to: block | list-item".
[x] What does class C mean? Is this situation possible in braille CSS? (Answer: I don't think so)
"Between the content edge of a block container box and the outer edges of its child content (margin edges of block-level children or line box edges for inline-level children) if there is a (non-zero) gap between them."
[ ] Explain simplifications with respect to original breaking rules [CSS3BREAK]: no block-perpendicular fragmentation, only one break type (what about volume breaks?), no monolithic elements, only normal flow, etc.
Paged Media
The ‘@page’ rule
@page:firstis defined as "matching the first printed page of a volume". However when it follows a page type selector should it instead match the first page of a sequence of pages of the specified type (i.e. similar to the way the volume pseudo-classes are defined), or not?@page:blank:left { ... }.Using Named Pages: the 'page' property
Page Breaking
Controlling Page Breaks
Rules for Page Breaking
See also