Skip to content

Commit 436d09b

Browse files
committed
[css-overflow] Record issues about paginated overflow
1 parent ecd1e08 commit 436d09b

File tree

2 files changed

+663
-0
lines changed

2 files changed

+663
-0
lines changed

css-overflow/Overview.bs

+23
Original file line numberDiff line numberDiff line change
@@ -569,6 +569,29 @@ This section introduces and defines the meaning of the ''continue/paginate'' val
569569

570570
Issue: Write this section
571571

572+
Issue: Pages should be possible to style with @page rules. How does that work for nested pages?
573+
574+
<div class="issue">
575+
Should traditional pagination (e.g. when printing)
576+
be expressed through some magic in the computed value of ''continue: next'',
577+
or by inserting this in the UA stylesheet:
578+
<pre><code class="lang-css">
579+
@media (overflow-block: paged), (overflow-block: optional-paged) {
580+
:root {
581+
continue: paginate;
582+
}
583+
}
584+
</code></pre>
585+
</div>
586+
587+
Issue: Traditional pagination (e.g. when printing) assumes that
588+
:root is contained in the page box,
589+
rather than having the page box be a pseudo element child of :root.
590+
Can we work around that using something similar to fragment boxes?
591+
Or maybe by having a fragment box (reproducing :root) inside a page box inside :root?
592+
593+
Issue: How does the page box model work when it is a child of a regular css box?
594+
572595
Issue: The initial proposal in [[CSS3GCPM]] and implemantation from Opera
573596
used 4 values instead of ''continue/paginate'':
574597
"paged-x | paged-y | paged-x-controls | paged-y-controls".

0 commit comments

Comments
 (0)