css-overflow/Overview.bs

changeset 15281
b1ba630bd42c
parent 15280
eb6bb2430f8e
child 15282
7c267346770f
     1.1 --- a/css-overflow/Overview.bs	Tue Mar 03 22:07:45 2015 +0100
     1.2 +++ b/css-overflow/Overview.bs	Tue Mar 03 22:08:58 2015 +0100
     1.3 @@ -569,6 +569,29 @@
     1.4  
     1.5  Issue: Write this section
     1.6  
     1.7 +Issue: Pages should be possible to style with @page rules. How does that work for nested pages?
     1.8 +
     1.9 +<div class="issue">
    1.10 +Should traditional pagination (e.g. when printing)
    1.11 +be expressed through some magic in the computed value of ''continue: next'',
    1.12 +or by inserting this in the UA stylesheet:
    1.13 +<pre><code class="lang-css">
    1.14 +@media (overflow-block: paged), (overflow-block: optional-paged) {
    1.15 +	:root {
    1.16 +		continue: paginate;
    1.17 +	}
    1.18 +}
    1.19 +</code></pre>
    1.20 +</div>
    1.21 +
    1.22 +Issue: Traditional pagination (e.g. when printing) assumes that
    1.23 +:root is contained in the page box,
    1.24 +rather than having the page box be a pseudo element child of :root.
    1.25 +Can we work around that using something similar to fragment boxes?
    1.26 +Or maybe by having a fragment box (reproducing :root) inside a page box inside :root?
    1.27 +
    1.28 +Issue: How does the page box model work when it is a child of a regular css box?
    1.29 +
    1.30  Issue: The initial proposal in [[CSS3GCPM]] and implemantation from Opera
    1.31  used 4 values instead of ''continue/paginate'':
    1.32  "paged-x | paged-y | paged-x-controls | paged-y-controls".

mercurial