changeset
[css-overflow] Introduce the 'continue' property
Tue, 24 Feb 2015 23:47:34 +0900
- author
- Florian Rivoal <[email protected]>
- date
- Tue, 24 Feb 2015 23:47:34 +0900
- changeset 15278
- 79f716a8ad8f
- parent 15277
- ec3666d1e63d
- child 15279
- c4cd57777348
[css-overflow] Introduce the 'continue' property
All sections that previously refered to the 'fragments' and 'paged-*'
values of overflow are also patched up to use the 'continue' property
instead.
| css-overflow/Overview.bs | file | annotate | diff | comparison | revisions | |
| css-overflow/Overview.html | file | annotate | diff | comparison | revisions |
1.1 --- a/css-overflow/Overview.bs Tue Feb 24 14:42:29 2015 +0900 1.2 +++ b/css-overflow/Overview.bs Tue Feb 24 23:47:34 2015 +0900 1.3 @@ -464,50 +464,96 @@ 1.4 'overflow-x' and 'overflow-y' instead? 1.5 </p> 1.6 1.7 -<h2 id="fragmentation-properties">Fragmentation properties</h2> 1.8 +<h2 id="fragmentation">Fragmentation of overflow</h2> 1.9 1.10 -Issue: This section is a WIP, and currently just holds bits of information that need to be massaged into proper form. 1.11 + <pre class=propdef> 1.12 + Name: continue 1.13 + Value: ''auto'' | ''overflow'' | ''paginate'' | ''fragments'' | ''discard'' | ''next'' 1.14 + Initial: ''auto'' 1.15 + Applies to: block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]] 1.16 + Inherited: no 1.17 + Percentages: N/A 1.18 + Media: visual 1.19 + Computed value: see below 1.20 + Animatable: no 1.21 + Canonical order: <abbr title="follows order of property value definition">per grammar</abbr> 1.22 + </pre> 1.23 1.24 - | ''paged-x'' | ''paged-y'' | ''paged-x-controls'' | ''paged-y-controls'' | ''fragments'' 1.25 +Issue: Naming is preliminary. 1.26 +This was initially proposed as 1.27 +"fragmentation: auto | none | break | clone | page" 1.28 +in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a> 1.29 1.30 - <p class="issue"> 1.31 - Are all 4 of the ''paged-*'' values really needed? 1.32 - </p> 1.33 +Note: ''continue: fragments'' replaces "overflow:fragments" 1.34 +from earlier versions of this specification, 1.35 +while ''continue: paginate'' replaces "overflow: paged-x | paged-y | paged-x-controls | paged-y-controls" 1.36 1.37 - <dl> 1.38 - <dt><dfn>paged-x</dfn> 1.39 - <dt><dfn>paged-y</dfn> 1.40 - <dt><dfn>paged-x-controls</dfn> 1.41 - <dt><dfn>paged-y-controls</dfn> 1.42 +Issue: The definitions below are vaguely worded, and need to be more specific. 1.43 + 1.44 + <dl dfn-for="continue" dfn-type="value"> 1.45 + <dt><dfn>auto</dfn> 1.46 + <dd>Behavior varies between the other values, depending on contex. 1.47 + See the section below on computed values for details. 1.48 + 1.49 + <dt><dfn>overflow</dfn> 1.50 + <dd>Content that doesn't fit overflows, according to the 'overflow' property 1.51 + 1.52 + <dt><dfn>discard</dfn> 1.53 + <dd>Content that doesn't fit is discarded at a fragmentation break 1.54 + 1.55 + Note: generalized from region-fragment: break; on the last region of a region chain 1.56 + <dt><dfn>next</dfn> 1.57 + <dd>Content that doesn't fit is pushed to the next region 1.58 + if the element is part of a region chain, 1.59 + or to the next page if the element is part of a page chain. If 1.60 + there isn't a next region or page, it overflows. 1.61 + 1.62 + Note: Behavior could have been to discard 1.63 + but discarding anything should be a very explicit behavior 1.64 + 1.65 + <dt><dfn>paginate</dfn> 1.66 + <dd>Content that doesn't fit paginates. 1.67 + This creates a paginated view inside the element 1.68 + similar to the way that 'overflow: scroll' creates a scrollable view. 1.69 + 1.70 + Pages can be styled with @page rules. 1.71 + 1.72 + Note: Print is effectively "continue: paginate" on the root. 1.73 + 1.74 + See <a href="#paginated-overflow">paginated overflow</a> 1.75 <dt><dfn>fragments</dfn> 1.76 - <dd> 1.77 - These values are collectively the <dfn dfn>fragmenting values</dfn>; 1.78 - they are defined in the sections on 1.79 - <a href="#paginated-overflow">paginated overflow</a> and 1.80 - <a href="#fragment-overflow">fragment overflow</a>. 1.81 - </dd> 1.82 + <dd>content that doesn't fit causes the element to copy itself and continue laying out. 1.83 + See <a href="#fragment-overflow">fragment overflow</a>. 1.84 </dl> 1.85 1.86 - <div class="issue"> 1.87 - Having split the overflow and fragmentation properties, this issue is no longer relevant, but there are 1.88 - useful bits of information in the thread, so I am leaving it here for now. 1.89 +Issue: There is some overlap between overflow, discard and next. 1.90 +Only 2 of the 3 ever make sense in any situation, 1.91 +even though it isn't always the same two. 1.92 +It may be possible to reduce this to 2 values. 1.93 +An earlier proposal combined discard and next into break, 1.94 +although this had the downside of making discard a non explicit behavior. 1.95 1.96 - There are <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a> 1.97 - about how overflow, overflow-style, overflow-x and overflow-y 1.98 - should work and interact with each other. 1.99 - Until consensus on this topic is reached, 1.100 - it is not completely clear which of these 1.101 - should be used for 1.102 - paged-x | paged-y | paged-x-controls | paged-y-controls | fragments 1.103 - </div> 1.104 - 1.105 +Note: For background discussions leading to this property, see these threads: 1.106 +<a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussion of overflow, overflow-x, overflow-y and overflow-style</a> and 1.107 +<a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">proposal for a fragmentation property</a> 1.108 1.109 <h2 id="paginated-overflow">Paginated overflow</h2> 1.110 1.111 -<p class="issue">overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as [[CSS3GCPM]] has?)</p> 1.112 +This section introduces and defines the meaning of the ''continue/paginate'' value of the 'continue' property. 1.113 1.114 -<p class="issue">Ability to display N pages at once 1.115 -rather than just one page at once?</p> 1.116 +Issue: Write this section 1.117 + 1.118 +Issue: The initial proposal in [[CSS3GCPM]] and implemantation from Opera 1.119 +used 4 values instead of ''continue/paginate'': 1.120 +"paged-x | paged-y | paged-x-controls | paged-y-controls". 1.121 +Should this property also include these values, 1.122 +or are they better handled as separate properties? 1.123 +(e.g.: "pagination-layout: auto | horizontal | vertical", "pagination-controls: auto | none") 1.124 + 1.125 +Issue: Ability to display N pages at once 1.126 +rather than just one page at once? 1.127 +Could this be a value of "pagination-layout", such as: 1.128 +"pagination-layout: horizontal 2;" 1.129 1.130 <p class="issue"> 1.131 The current implementation of paginated overflow uses 1.132 @@ -515,25 +561,22 @@ 1.133 rather than the 'overflow-style' property as proposed 1.134 in the [[CSS3GCPM]] draft 1.135 (which also matches the [[CSS3-MARQUEE]] proposal). 1.136 - We should probably switch away from 'overflow-style', 1.137 - but that's not 100% clear. 1.138 + or the 'continue' property as described here. 1.139 </p> 1.140 1.141 <h2 id="fragment-overflow">Fragment overflow</h2> 1.142 1.143 - <p> 1.144 - This section introduces and defines the meaning of 1.145 - the new ''fragments'' value of the 'overflow' property. 1.146 - </p> 1.147 +This section introduces and defines the meaning of 1.148 +the ''continue/fragments'' value of the 'continue' property. 1.149 1.150 <p> 1.151 - When the computed value of 'overflow' for an element is ''fragments'', 1.152 + When the computed value of 'continue' for an element is ''continue/fragments'', 1.153 and implementations would otherwise have created a box for the element, 1.154 then implementations must create a sequence of <dfn>fragment box</dfn>es 1.155 for that element. 1.156 - (It is possible for an element with ''overflow: fragments'' 1.157 + (It is possible for an element with ''continue: fragments'' 1.158 to generate only one <a>fragment box</a>. 1.159 - However, if an element's computed 'overflow' is not ''fragments'', 1.160 + However, if an element's computed 'continue' is not ''continue/fragments'', 1.161 then its box is not a <a>fragment box</a>.) 1.162 Every <a>fragment box</a> is a fragmentation container, 1.163 and any overflow 1.164 @@ -579,7 +622,7 @@ 1.165 equal-sized cards</title> 1.166 <style> 1.167 .in-cards { 1.168 - overflow: fragments; 1.169 + continue: fragments; 1.170 1.171 width: 13em; 1.172 height: 8em; 1.173 @@ -608,7 +651,7 @@ 1.174 </div> 1.175 1.176 <p class="issue"> 1.177 - We should specify that ''overflow: fragments'' does not apply 1.178 + We should specify that ''continue: fragments'' does not apply 1.179 to at least some table parts, 1.180 and perhaps other elements as well. 1.181 We need to determine exactly which ones. 1.182 @@ -669,11 +712,11 @@ 1.183 <h4 id="style-of-fragments">Styling of fragments</h4> 1.184 1.185 <p class="issue"> 1.186 - Should this apply to fragment overflow only, 1.187 - or also to paginated overflow? 1.188 + Should this apply to continue:fragments only, 1.189 + or also to continue:paginate? 1.190 (If it applies, 1.191 then stricter property restrictions would be needed 1.192 - for paginated overflow.) 1.193 + for continue:paginate.) 1.194 </p> 1.195 1.196 <p> 1.197 @@ -704,7 +747,7 @@ 1.198 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML> 1.199 <style> 1.200 .bouncy-columns { 1.201 - overflow: fragments; 1.202 + continue: fragments; 1.203 width: 6em; 1.204 height: 10em; 1.205 float: left; 1.206 @@ -731,19 +774,15 @@ 1.207 </div> 1.208 1.209 <p> 1.210 - Styling an ''::nth-fragment()'' pseudo-element with the 'overflow' 1.211 + Styling an ''::nth-fragment()'' pseudo-element with the 'continue' 1.212 property does take effect; 1.213 if a <a>fragment box</a> has a 1.214 - computed value of 'overflow' other than ''fragments'' 1.215 + computed value of 'continue' other than ''fragments'' 1.216 then that fragment box is the last fragment. 1.217 - However, overriding 'overflow' on the first fragment 1.218 + However, overriding 'continue' on the first fragment 1.219 does not cause the <a>fragment box</a> not to exist; 1.220 whether there are fragment boxes at all is determined by 1.221 the computed value of overflow for the element. 1.222 - <span class="issue">Need to reword this to refer to the 1.223 - appropriate choice of 'overflow-x' or 'overflow-y', 1.224 - and then point to rule about the handling of the other one 1.225 - of 'overflow-x' or 'overflow-y'.</span> 1.226 </p> 1.227 1.228 <p> 1.229 @@ -767,8 +806,8 @@ 1.230 Specifying other values of 'display', 'position', 1.231 or 'float' is permitted, but is not allowed to change 1.232 the computed value of 'display-inside'. 1.233 - (Since 'overflow', 'overflow-x', and 'overflow-y' only 1.234 - apply to block containers, flex containers, and grid containers 1.235 + (Since 'continue' only 1.236 + applies to block containers, flex containers, and grid containers 1.237 the computed value of 'display-inside' is always 1.238 ''display-inside/block'', ''display-inside/flex'', or 1.239 ''display-inside/grid''. 1.240 @@ -811,7 +850,7 @@ 1.241 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML> 1.242 <style> 1.243 .article { 1.244 - overflow: fragments; 1.245 + continue: fragments; 1.246 } 1.247 .article::nth-fragment(1) { 1.248 font-size: 1.5em; 1.249 @@ -834,9 +873,8 @@ 1.250 <h4 id="style-in-fragments">Styling inside fragments</h4> 1.251 1.252 <p class="issue"> 1.253 - Should this apply to fragment overflow only, 1.254 - or also to paginated overflow, 1.255 - or even to pagination across pages? 1.256 + Should this apply to continue:fragments only, 1.257 + or also to continue:paginate? 1.258 </p> 1.259 1.260 <p> 1.261 @@ -886,7 +924,7 @@ 1.262 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML> 1.263 <style> 1.264 .dark-columns { 1.265 - overflow: fragments; 1.266 + continue: fragments; 1.267 width: 6em; 1.268 height: 10em; 1.269 float: left; 1.270 @@ -993,7 +1031,7 @@ 1.271 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML> 1.272 <style> 1.273 .article { 1.274 - overflow: fragments; 1.275 + continue: fragments; 1.276 } 1.277 .article::first-letter { 1.278 font-size: 2em; 1.279 @@ -1020,7 +1058,7 @@ 1.280 1.281 <p class="issue"> 1.282 This specification should define useful behavior 1.283 - for all values of 'overflow' 1.284 + for all values of 'overflow' and 'continue' 1.285 in static media (such as print). 1.286 Current implementation behavior is quite poor and 1.287 produces unexpected results when authors have not considered
2.1 --- a/css-overflow/Overview.html Tue Feb 24 14:42:29 2015 +0900 2.2 +++ b/css-overflow/Overview.html Tue Feb 24 23:47:34 2015 +0900 2.3 @@ -278,7 +278,7 @@ 2.4 <li><a href="#border-box-overflow"><span class="secno">2.3</span> <span class="content">Border box overflow</span></a> 2.5 </ul> 2.6 <li><a href="#overflow-properties"><span class="secno">3</span> <span class="content">Overflow properties</span></a> 2.7 - <li><a href="#fragmentation-properties"><span class="secno">4</span> <span class="content">Fragmentation properties</span></a> 2.8 + <li><a href="#fragmentation"><span class="secno">4</span> <span class="content">Fragmentation of overflow</span></a> 2.9 <li><a href="#paginated-overflow"><span class="secno">5</span> <span class="content">Paginated overflow</span></a> 2.10 <li><a href="#fragment-overflow"><span class="secno">6</span> <span class="content">Fragment overflow</span></a> 2.11 <ul class="toc"> 2.12 @@ -795,100 +795,178 @@ 2.13 </p> 2.14 2.15 2.16 - <h2 class="heading settled" data-level="4" id="fragmentation-properties"><span class="secno">4. </span><span class="content">Fragmentation properties</span><a class="self-link" href="#fragmentation-properties"></a></h2> 2.17 + <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno">4. </span><span class="content">Fragmentation of overflow</span><a class="self-link" href="#fragmentation"></a></h2> 2.18 2.19 2.20 - <div>Issue: This section is a WIP, and currently just holds bits of information that need to be massaged into proper form. 2.21 + <table class="definition propdef"> 2.22 + <tbody> 2.23 + <tr> 2.24 + <th>Name: 2.25 + <td><dfn class="css" data-dfn-type="property" data-export="" id="propdef-continue">continue<a class="self-link" href="#propdef-continue"></a></dfn> 2.26 + <tr> 2.27 + <th>Value: 2.28 + <td class="prod"><a class="css" data-link-type="maybe" href="#valdef-overflow-auto">auto</a> <a data-link-type="grammar" href="http://dev.w3.org/csswg/css-values-3/#comb-one">|</a> <a class="css" data-link-type="maybe" href="#valdef-continue-overflow">overflow</a> <a data-link-type="grammar" href="http://dev.w3.org/csswg/css-values-3/#comb-one">|</a> <a class="css" data-link-type="maybe" href="#valdef-continue-paginate">paginate</a> <a data-link-type="grammar" href="http://dev.w3.org/csswg/css-values-3/#comb-one">|</a> <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a> <a data-link-type="grammar" href="http://dev.w3.org/csswg/css-values-3/#comb-one">|</a> <a class="css" data-link-type="maybe" href="#valdef-continue-discard">discard</a> <a data-link-type="grammar" href="http://dev.w3.org/csswg/css-values-3/#comb-one">|</a> <a class="css" data-link-type="maybe" href="#valdef-continue-next">next</a> 2.29 + <tr> 2.30 + <th>Initial: 2.31 + <td><a class="css" data-link-type="maybe" href="#valdef-overflow-auto">auto</a> 2.32 + <tr> 2.33 + <th>Applies to: 2.34 + <td>block containers <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a>, flex containers <a data-link-type="biblio" href="#biblio-css3-flexbox">[CSS3-FLEXBOX]</a>, and grid containers <a data-link-type="biblio" href="#biblio-css3-grid-layout">[CSS3-GRID-LAYOUT]</a> 2.35 + <tr> 2.36 + <th>Inherited: 2.37 + <td>no 2.38 + <tr> 2.39 + <th>Percentages: 2.40 + <td>N/A 2.41 + <tr> 2.42 + <th>Media: 2.43 + <td>visual 2.44 + <tr> 2.45 + <th>Computed value: 2.46 + <td>see below 2.47 + <tr> 2.48 + <th>Animatable: 2.49 + <td>no 2.50 + <tr> 2.51 + <th>Canonical order: 2.52 + <td><abbr title="follows order of property value definition">per grammar</abbr></table> 2.53 2.54 2.55 - <p>| <span class="css">paged-x</span> | <span class="css">paged-y</span> | <span class="css">paged-x-controls</span> | <span class="css">paged-y-controls</span> | <span class="css">fragments</span></p> 2.56 + <p class="issue" id="issue-715243a1"><a class="self-link" href="#issue-715243a1"></a>Naming is preliminary. 2.57 +This was initially proposed as 2.58 +"fragmentation: auto | none | break | clone | page" 2.59 +in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a></p> 2.60 + 2.61 + 2.62 + <p class="note" role="note">Note: <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: fragments</a> replaces "overflow:fragments" 2.63 +from earlier versions of this specification, 2.64 +while <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: paginate</a> replaces "overflow: paged-x | paged-y | paged-x-controls | paged-y-controls"</p> 2.65 + 2.66 + 2.67 + <p class="issue" id="issue-dcb4cf6c"><a class="self-link" href="#issue-dcb4cf6c"></a>The definitions below are vaguely worded, and need to be more specific.</p> 2.68 2.69 2.70 - <p class="issue" id="issue-74b71fcd"><a class="self-link" href="#issue-74b71fcd"></a> 2.71 - Are all 4 of the <span class="css">paged-*</span> values really needed? 2.72 - </p> 2.73 + <dl> 2.74 + 2.75 + <dt><dfn class="css" data-dfn-for="continue" data-dfn-type="value" data-export="" id="valdef-continue-auto">auto<a class="self-link" href="#valdef-continue-auto"></a></dfn> 2.76 + 2.77 + <dd>Behavior varies between the other values, depending on contex. 2.78 + See the section below on computed values for details. 2.79 2.80 + 2.81 + <dt><dfn class="css" data-dfn-for="continue" data-dfn-type="value" data-export="" id="valdef-continue-overflow">overflow<a class="self-link" href="#valdef-continue-overflow"></a></dfn> 2.82 + 2.83 + <dd>Content that doesn’t fit overflows, according to the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> property 2.84 + 2.85 + 2.86 + <dt><dfn class="css" data-dfn-for="continue" data-dfn-type="value" data-export="" id="valdef-continue-discard">discard<a class="self-link" href="#valdef-continue-discard"></a></dfn> 2.87 + 2.88 + <dd>Content that doesn’t fit is discarded at a fragmentation break 2.89 + 2.90 + 2.91 + <p class="note" role="note">Note: generalized from region-fragment: break; on the last region of a region chain</p> 2.92 + 2.93 + 2.94 + <dt><dfn class="css" data-dfn-for="continue" data-dfn-type="value" data-export="" id="valdef-continue-next">next<a class="self-link" href="#valdef-continue-next"></a></dfn> 2.95 + 2.96 + <dd>Content that doesn’t fit is pushed to the next region 2.97 + if the element is part of a region chain, 2.98 + or to the next page if the element is part of a page chain. If 2.99 + there isn’t a next region or page, it overflows. 2.100 + 2.101 + 2.102 + <p class="note" role="note">Note: Behavior could have been to discard 2.103 + but discarding anything should be a very explicit behavior</p> 2.104 + 2.105 + 2.106 + 2.107 + <dt><dfn class="css" data-dfn-for="continue" data-dfn-type="value" data-export="" id="valdef-continue-paginate">paginate<a class="self-link" href="#valdef-continue-paginate"></a></dfn> 2.108 + 2.109 + <dd>Content that doesn’t fit paginates. 2.110 + This creates a paginated view inside the element 2.111 + similar to the way that 'overflow: scroll' creates a scrollable view. 2.112 + 2.113 + 2.114 + <p>Pages can be styled with @page rules.</p> 2.115 + 2.116 + 2.117 + 2.118 + <p class="note" role="note">Note: Print is effectively "continue: paginate" on the root.</p> 2.119 + 2.120 + 2.121 + 2.122 + <p>See <a href="#paginated-overflow">paginated overflow</a></p> 2.123 + 2.124 + 2.125 + <dt><dfn class="css" data-dfn-for="continue" data-dfn-type="value" data-export="" id="valdef-continue-fragments">fragments<a class="self-link" href="#valdef-continue-fragments"></a></dfn> 2.126 + 2.127 + <dd>content that doesn’t fit causes the element to copy itself and continue laying out. 2.128 + See <a href="#fragment-overflow">fragment overflow</a>. 2.129 2.130 - <dl> 2.131 - 2.132 - <dt><dfn data-dfn-type="dfn" data-noexport="" id="paged_x">paged-x<a class="self-link" href="#paged_x"></a></dfn> 2.133 - 2.134 - <dt><dfn data-dfn-type="dfn" data-noexport="" id="paged_y">paged-y<a class="self-link" href="#paged_y"></a></dfn> 2.135 - 2.136 - <dt><dfn data-dfn-type="dfn" data-noexport="" id="paged_x_controls">paged-x-controls<a class="self-link" href="#paged_x_controls"></a></dfn> 2.137 - 2.138 - <dt><dfn data-dfn-type="dfn" data-noexport="" id="paged_y_controls">paged-y-controls<a class="self-link" href="#paged_y_controls"></a></dfn> 2.139 - 2.140 - <dt><dfn data-dfn-type="dfn" data-noexport="" id="fragments">fragments<a class="self-link" href="#fragments"></a></dfn> 2.141 - 2.142 - <dd> 2.143 - These values are collectively the <dfn data-dfn-type="dfn" data-noexport="" id="fragmenting-values">fragmenting values<a class="self-link" href="#fragmenting-values"></a></dfn>; 2.144 - they are defined in the sections on 2.145 - <a href="#paginated-overflow">paginated overflow</a> and 2.146 - <a href="#fragment-overflow">fragment overflow</a>. 2.147 - 2.148 - 2.149 - 2.150 - </dl> 2.151 + </dl> 2.152 2.153 - 2.154 - <div class="issue" id="issue-cd311d63"><a class="self-link" href="#issue-cd311d63"></a> 2.155 - Having split the overflow and fragmentation properties, this issue is no longer relevant, but there are 2.156 - useful bits of information in the thread, so I am leaving it here for now. 2.157 2.158 + <p class="issue" id="issue-0234f53f"><a class="self-link" href="#issue-0234f53f"></a>There is some overlap between overflow, discard and next. 2.159 +Only 2 of the 3 ever make sense in any situation, 2.160 +even though it isn’t always the same two. 2.161 +It may be possible to reduce this to 2 values. 2.162 +An earlier proposal combined discard and next into break, 2.163 +although this had the downside of making discard a non explicit behavior.</p> 2.164 2.165 - <p>There are <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a> 2.166 - about how overflow, overflow-style, overflow-x and overflow-y 2.167 - should work and interact with each other. 2.168 - Until consensus on this topic is reached, 2.169 - it is not completely clear which of these 2.170 - should be used for 2.171 - paged-x | paged-y | paged-x-controls | paged-y-controls | fragments</p> 2.172 - 2.173 - 2.174 - </div> 2.175 2.176 -</div> 2.177 + <p class="note" role="note">Note: For background discussions leading to this property, see these threads: 2.178 +<a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussion of overflow, overflow-x, overflow-y and overflow-style</a> and 2.179 +<a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">proposal for a fragmentation property</a></p> 2.180 2.181 2.182 <h2 class="heading settled" data-level="5" id="paginated-overflow"><span class="secno">5. </span><span class="content">Paginated overflow</span><a class="self-link" href="#paginated-overflow"></a></h2> 2.183 2.184 2.185 - <p class="issue" id="issue-0a5e0b64"><a class="self-link" href="#issue-0a5e0b64"></a>overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> has?)</p> 2.186 + <p>This section introduces and defines the meaning of the <a class="css" data-link-type="maybe" href="#valdef-continue-paginate">paginate</a> value of the <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> property.</p> 2.187 2.188 2.189 - <p class="issue" id="issue-22961e25"><a class="self-link" href="#issue-22961e25"></a>Ability to display N pages at once 2.190 -rather than just one page at once?</p> 2.191 + <p class="issue" id="issue-001d5014"><a class="self-link" href="#issue-001d5014"></a>Write this section</p> 2.192 + 2.193 + 2.194 + <p class="issue" id="issue-e9f64b3d"><a class="self-link" href="#issue-e9f64b3d"></a>The initial proposal in <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> and implemantation from Opera 2.195 +used 4 values instead of <a class="css" data-link-type="maybe" href="#valdef-continue-paginate">paginate</a>: 2.196 +"paged-x | paged-y | paged-x-controls | paged-y-controls". 2.197 +Should this property also include these values, 2.198 +or are they better handled as separate properties? 2.199 +(e.g.: "pagination-layout: auto | horizontal | vertical", "pagination-controls: auto | none")</p> 2.200 + 2.201 + 2.202 + <p class="issue" id="issue-55c97ed8"><a class="self-link" href="#issue-55c97ed8"></a>Ability to display N pages at once 2.203 +rather than just one page at once? 2.204 +Could this be a value of "pagination-layout", such as: 2.205 +"pagination-layout: horizontal 2;"</p> 2.206 2.207 2.208 - <p class="issue" id="issue-1f266e7d"><a class="self-link" href="#issue-1f266e7d"></a> 2.209 + <p class="issue" id="issue-360561bd"><a class="self-link" href="#issue-360561bd"></a> 2.210 The current implementation of paginated overflow uses 2.211 the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>/<a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a>/<a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> properties 2.212 rather than the <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> property as proposed 2.213 in the <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> draft 2.214 (which also matches the <a data-link-type="biblio" href="#biblio-css3-marquee">[CSS3-MARQUEE]</a> proposal). 2.215 - We should probably switch away from <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a>, 2.216 - but that’s not 100% clear. 2.217 + or the <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> property as described here. 2.218 </p> 2.219 2.220 2.221 <h2 class="heading settled" data-level="6" id="fragment-overflow"><span class="secno">6. </span><span class="content">Fragment overflow</span><a class="self-link" href="#fragment-overflow"></a></h2> 2.222 2.223 - 2.224 - <p> 2.225 - This section introduces and defines the meaning of 2.226 - the new <span class="css">fragments</span> value of the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> property. 2.227 - </p> 2.228 + 2.229 + <p>This section introduces and defines the meaning of 2.230 +the <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a> value of the <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> property.</p> 2.231 2.232 2.233 <p> 2.234 - When the computed value of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> for an element is <span class="css">fragments</span>, 2.235 + When the computed value of <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> for an element is <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a>, 2.236 and implementations would otherwise have created a box for the element, 2.237 then implementations must create a sequence of <dfn data-dfn-type="dfn" data-noexport="" id="fragment-box">fragment box<a class="self-link" href="#fragment-box"></a></dfn>es 2.238 for that element. 2.239 - (It is possible for an element with <a class="css" data-link-type="propdesc" href="#propdef-overflow">overflow: fragments</a> 2.240 + (It is possible for an element with <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: fragments</a> 2.241 to generate only one <a data-link-type="dfn" href="#fragment-box">fragment box</a>. 2.242 - However, if an element’s computed <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> is not <span class="css">fragments</span>, 2.243 + However, if an element’s computed <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> is not <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a>, 2.244 then its box is not a <a data-link-type="dfn" href="#fragment-box">fragment box</a>.) 2.245 Every <a data-link-type="dfn" href="#fragment-box">fragment box</a> is a fragmentation container, 2.246 and any overflow 2.247 @@ -941,7 +1019,7 @@ 2.248 equal-sized cards</title> 2.249 <style> 2.250 .in-cards { 2.251 - overflow: fragments; 2.252 + continue: fragments; 2.253 2.254 width: 13em; 2.255 height: 8em; 2.256 @@ -978,8 +1056,8 @@ 2.257 </div> 2.258 2.259 2.260 - <p class="issue" id="issue-7c2776be"><a class="self-link" href="#issue-7c2776be"></a> 2.261 - We should specify that <a class="css" data-link-type="propdesc" href="#propdef-overflow">overflow: fragments</a> does not apply 2.262 + <p class="issue" id="issue-25a84ff4"><a class="self-link" href="#issue-25a84ff4"></a> 2.263 + We should specify that <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: fragments</a> does not apply 2.264 to at least some table parts, 2.265 and perhaps other elements as well. 2.266 We need to determine exactly which ones. 2.267 @@ -1048,12 +1126,12 @@ 2.268 <h4 class="heading settled" data-level="6.1.2" id="style-of-fragments"><span class="secno">6.1.2. </span><span class="content">Styling of fragments</span><a class="self-link" href="#style-of-fragments"></a></h4> 2.269 2.270 2.271 - <p class="issue" id="issue-27c56696"><a class="self-link" href="#issue-27c56696"></a> 2.272 - Should this apply to fragment overflow only, 2.273 - or also to paginated overflow? 2.274 + <p class="issue" id="issue-6e8f615f"><a class="self-link" href="#issue-6e8f615f"></a> 2.275 + Should this apply to continue:fragments only, 2.276 + or also to continue:paginate? 2.277 (If it applies, 2.278 then stricter property restrictions would be needed 2.279 - for paginated overflow.) 2.280 + for continue:paginate.) 2.281 </p> 2.282 2.283 2.284 @@ -1092,7 +1170,7 @@ 2.285 <pre><!DOCTYPE HTML> 2.286 <style> 2.287 .bouncy-columns { 2.288 - overflow: fragments; 2.289 + continue: fragments; 2.290 width: 6em; 2.291 height: 10em; 2.292 float: left; 2.293 @@ -1130,19 +1208,15 @@ 2.294 2.295 2.296 <p> 2.297 - Styling an <a class="css" data-link-type="maybe" href="#selectordef-nth-fragment">::nth-fragment()</a> pseudo-element with the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> 2.298 + Styling an <a class="css" data-link-type="maybe" href="#selectordef-nth-fragment">::nth-fragment()</a> pseudo-element with the <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> 2.299 property does take effect; 2.300 if a <a data-link-type="dfn" href="#fragment-box">fragment box</a> has a 2.301 - computed value of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> other than <span class="css">fragments</span> 2.302 + computed value of <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> other than <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a> 2.303 then that fragment box is the last fragment. 2.304 - However, overriding <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> on the first fragment 2.305 + However, overriding <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> on the first fragment 2.306 does not cause the <a data-link-type="dfn" href="#fragment-box">fragment box</a> not to exist; 2.307 whether there are fragment boxes at all is determined by 2.308 the computed value of overflow for the element. 2.309 - <span class="issue" id="issue-1c902202"><a class="self-link" href="#issue-1c902202"></a>Need to reword this to refer to the 2.310 - appropriate choice of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> or <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>, 2.311 - and then point to rule about the handling of the other one 2.312 - of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> or <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>.</span> 2.313 </p> 2.314 2.315 2.316 @@ -1169,8 +1243,8 @@ 2.317 Specifying other values of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css2/visuren.html#propdef-display">display</a>, <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-position-3/#position">position</a>, 2.318 or <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css2/visuren.html#propdef-float">float</a> is permitted, but is not allowed to change 2.319 the computed value of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-inside">display-inside</a>. 2.320 - (Since <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>, <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a>, and <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> only 2.321 - apply to block containers, flex containers, and grid containers 2.322 + (Since <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> only 2.323 + applies to block containers, flex containers, and grid containers 2.324 the computed value of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-inside">display-inside</a> is always 2.325 <span class="css">block</span>, <span class="css">flex</span>, or 2.326 <span class="css">grid</span>. 2.327 @@ -1222,7 +1296,7 @@ 2.328 <pre><!DOCTYPE HTML> 2.329 <style> 2.330 .article { 2.331 - overflow: fragments; 2.332 + continue: fragments; 2.333 } 2.334 .article::nth-fragment(1) { 2.335 font-size: 1.5em; 2.336 @@ -1254,10 +1328,9 @@ 2.337 <h4 class="heading settled" data-level="6.1.3" id="style-in-fragments"><span class="secno">6.1.3. </span><span class="content">Styling inside fragments</span><a class="self-link" href="#style-in-fragments"></a></h4> 2.338 2.339 2.340 - <p class="issue" id="issue-b1e468e3"><a class="self-link" href="#issue-b1e468e3"></a> 2.341 - Should this apply to fragment overflow only, 2.342 - or also to paginated overflow, 2.343 - or even to pagination across pages? 2.344 + <p class="issue" id="issue-d00a7cbb"><a class="self-link" href="#issue-d00a7cbb"></a> 2.345 + Should this apply to continue:fragments only, 2.346 + or also to continue:paginate? 2.347 </p> 2.348 2.349 2.350 @@ -1323,7 +1396,7 @@ 2.351 <pre><!DOCTYPE HTML> 2.352 <style> 2.353 .dark-columns { 2.354 - overflow: fragments; 2.355 + continue: fragments; 2.356 width: 6em; 2.357 height: 10em; 2.358 float: left; 2.359 @@ -1484,7 +1557,7 @@ 2.360 <pre><!DOCTYPE HTML> 2.361 <style> 2.362 .article { 2.363 - overflow: fragments; 2.364 + continue: fragments; 2.365 } 2.366 .article::first-letter { 2.367 font-size: 2em; 2.368 @@ -1521,9 +1594,9 @@ 2.369 <h2 class="heading settled" data-level="7" id="static-media"><span class="secno">7. </span><span class="content">Overflow in static media</span><a class="self-link" href="#static-media"></a></h2> 2.370 2.371 2.372 - <p class="issue" id="issue-5ad703cc"><a class="self-link" href="#issue-5ad703cc"></a> 2.373 + <p class="issue" id="issue-de91ba9b"><a class="self-link" href="#issue-de91ba9b"></a> 2.374 This specification should define useful behavior 2.375 - for all values of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> 2.376 + for all values of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> and <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> 2.377 in static media (such as print). 2.378 Current implementation behavior is quite poor and 2.379 produces unexpected results when authors have not considered 2.380 @@ -1727,19 +1800,25 @@ 2.381 <ul class="indexlist"> 2.382 <li>3d-preserving child, <a href="#3d_preserving-child">2.2</a> 2.383 <li>3d-preserving descendant, <a href="#3d_preserving-descendant">2.2</a> 2.384 - <li>auto, <a href="#valdef-overflow-auto">3</a> 2.385 + <li>auto 2.386 + <ul> 2.387 + <li>value for overflow, <a href="#valdef-overflow-auto">3</a> 2.388 + <li>value for continue, <a href="#valdef-continue-auto">4</a> 2.389 + </ul> 2.390 <li>border-box overflow, <a href="#border_box-overflow">2.3</a> 2.391 <li>border-box overflow rectangle, <a href="#border_box-overflow-rectangle">2.3</a> 2.392 <li>border-box overflow region, <a href="#border_box-overflow-region">2.3</a> 2.393 + <li>continue, <a href="#propdef-continue">4</a> 2.394 + <li>discard, <a href="#valdef-continue-discard">4</a> 2.395 <li>fragment box, <a href="#fragment-box">6</a> 2.396 - <li>fragmenting values, <a href="#fragmenting-values">4</a> 2.397 - <li>fragments, <a href="#fragments">4</a> 2.398 + <li>fragments, <a href="#valdef-continue-fragments">4</a> 2.399 <li>hidden, <a href="#valdef-overflow-hidden">3</a> 2.400 <li>ink overflow, <a href="#ink-overflow0">2.1</a> 2.401 <li>ink overflow rectangle, <a href="#ink-overflow-rectangle">2.1</a> 2.402 <li>ink overflow region, <a href="#ink-overflow-region">2.1</a> 2.403 <li><integer>, <a href="#valdef-max-lines-integer">6.2</a> 2.404 <li>max-lines, <a href="#propdef-max-lines">6.2</a> 2.405 + <li>next, <a href="#valdef-continue-next">4</a> 2.406 <li>non-3d-preserving child, <a href="#non_3d_preserving-child">2.2</a> 2.407 <li>none, <a href="#valdef-max-lines-none">6.2</a> 2.408 <li>::nth-fragment(), <a href="#selectordef-nth-fragment">6.1.1</a> 2.409 @@ -1747,13 +1826,11 @@ 2.410 <ul> 2.411 <li>definition of, <a href="#overflow">2</a> 2.412 <li>(property), <a href="#propdef-overflow">3</a> 2.413 + <li>value for continue, <a href="#valdef-continue-overflow">4</a> 2.414 </ul> 2.415 <li>overflow-x, <a href="#propdef-overflow-x">3</a> 2.416 <li>overflow-y, <a href="#propdef-overflow-y">3</a> 2.417 - <li>paged-x, <a href="#paged_x">4</a> 2.418 - <li>paged-x-controls, <a href="#paged_x_controls">4</a> 2.419 - <li>paged-y, <a href="#paged_y">4</a> 2.420 - <li>paged-y-controls, <a href="#paged_y_controls">4</a> 2.421 + <li>paginate, <a href="#valdef-continue-paginate">4</a> 2.422 <li>scroll, <a href="#valdef-overflow-scroll">3</a> 2.423 <li>scrollable overflow, <a href="#scrollable-overflow0">2.2</a> 2.424 <li>scrollable overflow rectangle, <a href="#scrollable-overflow-rectangle">2.2</a> 2.425 @@ -1903,6 +1980,17 @@ 2.426 <td>per grammar 2.427 <td>see individual properties 2.428 <tr> 2.429 + <th scope="row"><a class="css" data-link-type="property" href="#propdef-continue">continue</a> 2.430 + <td>auto | overflow | paginate | fragments | discard | next 2.431 + <td>auto 2.432 + <td>block containers [CSS21], flex containers [CSS3-FLEXBOX], and grid containers [CSS3-GRID-LAYOUT] 2.433 + <td>no 2.434 + <td>N/A 2.435 + <td>visual 2.436 + <td>no 2.437 + <td>per grammar 2.438 + <td>see below 2.439 + <tr> 2.440 <th scope="row"><a class="css" data-link-type="property" href="#propdef-max-lines">max-lines</a> 2.441 <td>none | <integer> 2.442 <td>none 2.443 @@ -1969,36 +2057,36 @@ 2.444 despite that implementations have implemented 2.445 <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> and <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> instead? 2.446 <a href="#issue-52e2a181"> ↵ </a></div> 2.447 - <div class="issue"> 2.448 - Are all 4 of the <span class="css">paged-*</span> values really needed? 2.449 - <a href="#issue-74b71fcd"> ↵ </a></div> 2.450 - <div class="issue"> 2.451 - Having split the overflow and fragmentation properties, this issue is no longer relevant, but there are 2.452 - useful bits of information in the thread, so I am leaving it here for now. 2.453 - 2.454 - 2.455 - <p>There are <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a> 2.456 - about how overflow, overflow-style, overflow-x and overflow-y 2.457 - should work and interact with each other. 2.458 - Until consensus on this topic is reached, 2.459 - it is not completely clear which of these 2.460 - should be used for 2.461 - paged-x | paged-y | paged-x-controls | paged-y-controls | fragments</p> 2.462 - 2.463 - <a href="#issue-cd311d63"> ↵ </a> 2.464 - </div> 2.465 - <div class="issue">overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> has?)<a href="#issue-0a5e0b64"> ↵ </a></div> 2.466 + <div class="issue">Naming is preliminary. 2.467 +This was initially proposed as 2.468 +"fragmentation: auto | none | break | clone | page" 2.469 +in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a><a href="#issue-715243a1"> ↵ </a></div> 2.470 + <div class="issue">The definitions below are vaguely worded, and need to be more specific.<a href="#issue-dcb4cf6c"> ↵ </a></div> 2.471 + <div class="issue">There is some overlap between overflow, discard and next. 2.472 +Only 2 of the 3 ever make sense in any situation, 2.473 +even though it isn’t always the same two. 2.474 +It may be possible to reduce this to 2 values. 2.475 +An earlier proposal combined discard and next into break, 2.476 +although this had the downside of making discard a non explicit behavior.<a href="#issue-0234f53f"> ↵ </a></div> 2.477 + <div class="issue">Write this section<a href="#issue-001d5014"> ↵ </a></div> 2.478 + <div class="issue">The initial proposal in <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> and implemantation from Opera 2.479 +used 4 values instead of <a class="css" data-link-type="maybe" href="#valdef-continue-paginate">paginate</a>: 2.480 +"paged-x | paged-y | paged-x-controls | paged-y-controls". 2.481 +Should this property also include these values, 2.482 +or are they better handled as separate properties? 2.483 +(e.g.: "pagination-layout: auto | horizontal | vertical", "pagination-controls: auto | none")<a href="#issue-e9f64b3d"> ↵ </a></div> 2.484 <div class="issue">Ability to display N pages at once 2.485 -rather than just one page at once?<a href="#issue-22961e25"> ↵ </a></div> 2.486 +rather than just one page at once? 2.487 +Could this be a value of "pagination-layout", such as: 2.488 +"pagination-layout: horizontal 2;"<a href="#issue-55c97ed8"> ↵ </a></div> 2.489 <div class="issue"> 2.490 The current implementation of paginated overflow uses 2.491 the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>/<a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a>/<a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> properties 2.492 rather than the <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> property as proposed 2.493 in the <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> draft 2.494 (which also matches the <a data-link-type="biblio" href="#biblio-css3-marquee">[CSS3-MARQUEE]</a> proposal). 2.495 - We should probably switch away from <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a>, 2.496 - but that’s not 100% clear. 2.497 - <a href="#issue-1f266e7d"> ↵ </a></div> 2.498 + or the <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> property as described here. 2.499 + <a href="#issue-360561bd"> ↵ </a></div> 2.500 <div class="issue">Or is it as though it’s a next sibling of 2.501 the element? Need to figure out exactly how this interacts with 2.502 other box-level fixup.<a href="#issue-74f423ed"> ↵ </a></div> 2.503 @@ -2015,11 +2103,11 @@ 2.504 despite that the name seems the most logical name for such a feature. 2.505 <a href="#issue-c4f3aedb"> ↵ </a></div> 2.506 <div class="issue"> 2.507 - We should specify that <a class="css" data-link-type="propdesc" href="#propdef-overflow">overflow: fragments</a> does not apply 2.508 + We should specify that <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: fragments</a> does not apply 2.509 to at least some table parts, 2.510 and perhaps other elements as well. 2.511 We need to determine exactly which ones. 2.512 - <a href="#issue-7c2776be"> ↵ </a></div> 2.513 + <a href="#issue-25a84ff4"> ↵ </a></div> 2.514 <div class="issue"> 2.515 This specification needs to say which type of 2.516 fragmentation context is created 2.517 @@ -2046,18 +2134,14 @@ 2.518 the new <span class="css">::fragment:nth(an+b)</span> syntax. 2.519 <a href="#issue-0e3bec77"> ↵ </a></div> 2.520 <div class="issue"> 2.521 - Should this apply to fragment overflow only, 2.522 - or also to paginated overflow? 2.523 + Should this apply to continue:fragments only, 2.524 + or also to continue:paginate? 2.525 (If it applies, 2.526 then stricter property restrictions would be needed 2.527 - for paginated overflow.) 2.528 - <a href="#issue-27c56696"> ↵ </a></div> 2.529 + for continue:paginate.) 2.530 + <a href="#issue-6e8f615f"> ↵ </a></div> 2.531 <div class="issue">Does this need to be specified in 2.532 the cascading module as well?<a href="#issue-8f881f96"> ↵ </a></div> 2.533 - <div class="issue">Need to reword this to refer to the 2.534 - appropriate choice of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> or <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>, 2.535 - and then point to rule about the handling of the other one 2.536 - of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> or <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>.<a href="#issue-1c902202"> ↵ </a></div> 2.537 <div class="issue">Need to specify exactly how this works, 2.538 but it depends on 2.539 having <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-inside">display-inside</a> and <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-outside">display-outside</a> specified.<a href="#issue-d98e732d"> ↵ </a></div> 2.540 @@ -2072,10 +2156,9 @@ 2.541 should also apply to inheritance from fragments. 2.542 <a href="#issue-d95b27f9"> ↵ </a></div> 2.543 <div class="issue"> 2.544 - Should this apply to fragment overflow only, 2.545 - or also to paginated overflow, 2.546 - or even to pagination across pages? 2.547 - <a href="#issue-b1e468e3"> ↵ </a></div> 2.548 + Should this apply to continue:fragments only, 2.549 + or also to continue:paginate? 2.550 + <a href="#issue-d00a7cbb"> ↵ </a></div> 2.551 <div class="issue"> 2.552 If there are multiple boundaries between this line 2.553 and the previous, where exactly (in terms of element 2.554 @@ -2085,13 +2168,13 @@ 2.555 to pagination?<a href="#issue-1527f8dd"> ↵ </a></div> 2.556 <div class="issue"> 2.557 This specification should define useful behavior 2.558 - for all values of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> 2.559 + for all values of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> and <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> 2.560 in static media (such as print). 2.561 Current implementation behavior is quite poor and 2.562 produces unexpected results when authors have not considered 2.563 what will happen when 2.564 the content they produce for interactive media 2.565 is printed. 2.566 - <a href="#issue-5ad703cc"> ↵ </a></div> 2.567 + <a href="#issue-de91ba9b"> ↵ </a></div> 2.568 </div></body> 2.569 </html> 2.570 \ No newline at end of file
