Mercurial > drafts / changeset

     1.1 --- a/css-overflow/Overview.bs	Tue Mar 03 22:08:58 2015 +0100
     1.2 +++ b/css-overflow/Overview.bs	Tue Mar 03 22:19:48 2015 +0100
     1.3 @@ -488,6 +488,11 @@
     1.4  		Canonical order: <abbr title="follows order of property value definition">per grammar</abbr>
     1.5  	</pre>
     1.6  
     1.7 +Issue: The naming of this property and its values is preliminary.
     1.8 +This was initially proposed as
     1.9 +"fragmentation: auto | none | break | clone | page"
    1.10 +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.11 +and there is not yet wide agreement as to which naming is better.
    1.12  
    1.13  Note: ''continue: fragments'' replaces "overflow:fragments"
    1.14  from earlier versions of this specification,
    1.15 @@ -549,11 +554,6 @@
    1.16  	<li>In all other cases, the computed value is the specified value
    1.17  </ol>
    1.18  
    1.19 -Issue: The naming of this property and its values is preliminary.
    1.20 -This was initially proposed as
    1.21 -"fragmentation: auto | none | break | clone | page"
    1.22 -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.23 -
    1.24  Issue: If we introduce a pseudo element that can select columns in a multicol,
    1.25  we would need to specify that next computes to next on it,
    1.26  or introduce a new value and have next compute to that

     2.1 --- a/css-overflow/Overview.html	Tue Mar 03 22:08:58 2015 +0100
     2.2 +++ b/css-overflow/Overview.html	Tue Mar 03 22:19:48 2015 +0100
     2.3 @@ -1435,6 +1435,12 @@
     2.4        <td><abbr title="follows order of property value definition">per grammar</abbr></table>
     2.5  
     2.6  
     2.7 +   <p class="issue" id="issue-b2c6e3da"><a class="self-link" href="#issue-b2c6e3da"></a>The naming of this property and its values is preliminary.
     2.8 +This was initially proposed as
     2.9 +"fragmentation: auto | none | break | clone | page"
    2.10 +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>,
    2.11 +and there is not yet wide agreement as to which naming is better.</p>
    2.12 +
    2.13  
    2.14     <p class="note" role="note">Note: <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: fragments</a> replaces "overflow:fragments"
    2.15  from earlier versions of this specification,
    2.16 @@ -1536,12 +1542,6 @@
    2.17  </ol>
    2.18  
    2.19  
    2.20 -   <p class="issue" id="issue-77a336c3"><a class="self-link" href="#issue-77a336c3"></a>The naming of this property and its values is preliminary.
    2.21 -This was initially proposed as
    2.22 -"fragmentation: auto | none | break | clone | page"
    2.23 -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.24 -
    2.25 -
    2.26     <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.27  we would need to specify that next computes to next on it,
    2.28  or introduce a new value and have next compute to that
    2.29 @@ -2752,13 +2752,14 @@
    2.30  		despite that implementations have implemented
    2.31  		<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.32  	<a href="#issue-52e2a181"> ↵ </a></div>
    2.33 +   <div class="issue">The naming of this property and its values is preliminary.
    2.34 +This was initially proposed as
    2.35 +"fragmentation: auto | none | break | clone | page"
    2.36 +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>,
    2.37 +and there is not yet wide agreement as to which naming is better.<a href="#issue-b2c6e3da"> ↵ </a></div>
    2.38     <div class="issue">When the element isn’t a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-break-3/#fragmentation-container">fragmentation container</a> already,
    2.39  		should this work by turning it directly into one,
    2.40  		or by creating a <a data-link-type="dfn" href="#fragment-box">fragment box</a> inside it like <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a> does?<a href="#issue-36be54be"> ↵ </a></div>
    2.41 -   <div class="issue">The naming of this property and its values is preliminary.
    2.42 -This was initially proposed as
    2.43 -"fragmentation: auto | none | break | clone | page"
    2.44 -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.45     <div class="issue">If we introduce a pseudo element that can select columns in a multicol,
    2.46  we would need to specify that next computes to next on it,
    2.47  or introduce a new value and have next compute to that