Tue, 03 Mar 2015 22:07:45 +0100
[css-overflow] record issue about multicol
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 Sat Feb 28 01:53:36 2015 +0900 1.2 +++ b/css-overflow/Overview.bs Tue Mar 03 22:07:45 2015 +0100 1.3 @@ -554,6 +554,11 @@ 1.4 "fragmentation: auto | none | break | clone | page" 1.5 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.6 1.7 +Issue: If we introduce a pseudo element that can select columns in a multicol, 1.8 +we would need to specify that next computes to next on it, 1.9 +or introduce a new value and have next compute to that 1.10 +(but what would that value compute to on things that aren't columns?). 1.11 + 1.12 Note: For background discussions leading to this property, see these threads: 1.13 <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.14 <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">proposal for a fragmentation property</a>
2.1 --- a/css-overflow/Overview.html Sat Feb 28 01:53:36 2015 +0900 2.2 +++ b/css-overflow/Overview.html Tue Mar 03 22:07:45 2015 +0100 2.3 @@ -950,6 +950,12 @@ 2.4 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.5 2.6 2.7 + <p class="issue" id="issue-598fb492"><a class="self-link" href="#issue-598fb492"></a>If we introduce a pseudo element that can select columns in a multicol, 2.8 +we would need to specify that next computes to next on it, 2.9 +or introduce a new value and have next compute to that 2.10 +(but what would that value compute to on things that arenât columns?).</p> 2.11 + 2.12 + 2.13 <p class="note" role="note">Note: For background discussions leading to this property, see these threads: 2.14 <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.15 <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">proposal for a fragmentation property</a></p> 2.16 @@ -2134,6 +2140,10 @@ 2.17 This was initially proposed as 2.18 "fragmentation: auto | none | break | clone | page" 2.19 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-77a336c3"> âµ </a></div> 2.20 + <div class="issue">If we introduce a pseudo element that can select columns in a multicol, 2.21 +we would need to specify that next computes to next on it, 2.22 +or introduce a new value and have next compute to that 2.23 +(but what would that value compute to on things that arenât columns?).<a href="#issue-598fb492"> âµ </a></div> 2.24 <div class="issue">Write this section<a href="#issue-001d5014"> âµ </a></div> 2.25 <div class="issue">The initial proposal in <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> and implemantation from Opera 2.26 used 4 values instead of <a class="css" data-link-type="maybe" href="#valdef-continue-paginate">paginate</a>: