[css-overflow] Call the intial value of continue auto rather than next

Author: frivoal

css-overflow/Overview.bs

@@ -380,7 +380,7 @@ Introduction</h2>
 
 	<pre class=propdef>
 		Name: overflow-x, overflow-y
-		Value: ''visible'' | ''hidden'' | ''scroll'' | ''auto''
+		Value: ''visible'' | ''hidden'' | ''scroll'' | ''overflow/auto''
 		Initial: ''visible''
 		Applies to: block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
 		Inherited: no
@@ -399,7 +399,7 @@ Introduction</h2>
 
 	<pre class=propdef>
 		Name: overflow
-		Value: ''visible'' | ''hidden'' | ''scroll'' | ''auto''
+		Value: ''visible'' | ''hidden'' | ''scroll'' | ''overflow/auto''
 		Initial: see individual properties
 		Applies to: block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
 		Inherited: no
@@ -477,8 +477,8 @@ and extends it further.
 
 	<pre class=propdef>
 		Name: continue
-		Value: ''next'' | ''overflow'' | ''paginate'' | ''fragments'' | ''discard''
-		Initial: next
+		Value: ''continue/auto'' | ''overflow'' | ''paginate'' | ''fragments'' | ''discard''
+		Initial: auto
 		Applies to: block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
 		Inherited: no
 		Percentages: N/A
@@ -503,13 +503,13 @@ from earlier versions of this specification,
 while ''continue: paginate'' replaces "overflow: paged-x | paged-y | paged-x-controls | paged-y-controls"
 
 	<dl dfn-for="continue" dfn-type="value">
-		<dt><dfn>next</dfn>
-		<dd>Content that doesn't fit is pushed to the next region
+		<dt><dfn>auto</dfn>
+		<dd>''continue/auto'' may only occur as a computed value
 		if the element is a <a spec="css-regions">CSS Region</a>
-		other than the last one in a <a spec="css-regions">region chain</a>,
-		or to the next page if the element is part of a page chain,
-		or to the next <a>fragment box</a> if the element is a <a>fragment box</a>
-		Otherwise, it overflows.
+		other than the last one in a <a spec="css-regions">region chain</a>.
+		Content that doesn't fit is pushed to the next region of the chain.
+
+		In all other cases, ''continue/auto'' computes to one of the other values.
 
 		<dt><dfn>overflow</dfn>
 		<dd>Content that doesn't fit overflows, according to the 'overflow' property
@@ -539,10 +539,10 @@ while ''continue: paginate'' replaces "overflow: paged-x | paged-y | paged-x-con
 
 The computed value of the 'continue' for a given element or pseudo element is determined as follow:
 <ol>
-	<li>If the specified value is ''continue/next''
+	<li>If the specified value is ''continue/auto''
 	<ol>
 		<li>On a <a spec="css-regions">CSS Region</a> other than the last one in a <a spec="css-regions">region chain</a>,
-		the computed value is ''continue/next''
+		the computed value is ''continue/auto''
 		<li>On a page
 		the computed value is ''continue/paginate''
 		<li>On a <a>fragment box</a>
@@ -559,8 +559,8 @@ The computed value of the 'continue' for a given element or pseudo element is de
 </ol>
 
 Issue: If we introduce a pseudo element that can select columns in a multicol,
-we would need to specify that next computes to next on it,
-or introduce a new value and have next compute to that
+we would need to specify that auto computes to auto on it,
+or introduce a new value and have auto compute to that
 (but what would that value compute to on things that aren't columns?).
 
 Note: For background discussions leading to this property, see these threads:
@@ -577,7 +577,7 @@ Issue: Pages should be possible to style with @page rules. How does that work fo
 
 <div class="issue">
 Should traditional pagination (e.g. when printing)
-be expressed through some magic in the computed value of ''continue: next'',
+be expressed through some magic in the computed value of ''continue/auto'',
 or by inserting this in the UA stylesheet:
 <pre><code class="lang-css">
 @media (overflow-block: paged), (overflow-block: optional-paged) {

css-overflow/Overview.html

@@ -767,7 +767,7 @@
    <h1 class="p-name no-ref" id="title">CSS Overflow Module Level 3</h1>
 
    <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft,
-    <time class="dt-updated" datetime="2015-03-03">3 March 2015</time></span></h2>
+    <time class="dt-updated" datetime="2015-03-11">11 March 2015</time></span></h2>
 
    <div data-fill-with="spec-metadata">
     <dl>
@@ -1408,10 +1408,10 @@ <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno
       <td><dfn class="css" data-dfn-type="property" data-export="" id="propdef-continue">continue<a class="self-link" href="#propdef-continue"></a></dfn>
      <tr>
       <th>Value:
-      <td class="prod"><a class="css" data-link-type="maybe" href="#valdef-continue-next">next</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>
+      <td class="prod"><a class="css" data-link-type="maybe" href="#valdef-continue-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>
      <tr>
       <th>Initial:
-      <td>next
+      <td>auto
      <tr>
       <th>Applies to:
       <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>
@@ -1454,14 +1454,16 @@ <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno
 
    <dl>
 
-    <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>
+    <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>
 
-    <dd>Content that doesn’t fit is pushed to the next region
+    <dd><a class="css" data-link-type="maybe" href="#valdef-continue-auto">auto</a> may only occur as a computed value
 		if the element is a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-regions-1/#css-region">CSS Region</a>
-		other than the last one in a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-regions-1/#region-chain">region chain</a>,
-		or to the next page if the element is part of a page chain,
-		or to the next <a data-link-type="dfn" href="#fragment-box">fragment box</a> if the element is a <a data-link-type="dfn" href="#fragment-box">fragment box</a>
-		Otherwise, it overflows.
+		other than the last one in a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-regions-1/#region-chain">region chain</a>.
+		Content that doesn’t fit is pushed to the next region of the chain.
+
+
+     <p>In all other cases, <a class="css" data-link-type="maybe" href="#valdef-continue-auto">auto</a> computes to one of the other values.</p>
+     
 
 
     <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>
@@ -1513,12 +1515,12 @@ <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno
 
    <ol>
 
-    <li>If the specified value is <a class="css" data-link-type="maybe" href="#valdef-continue-next">next</a>
+    <li>If the specified value is <a class="css" data-link-type="maybe" href="#valdef-continue-auto">auto</a>
 
      <ol>
 
       <li>On a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-regions-1/#css-region">CSS Region</a> other than the last one in a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-regions-1/#region-chain">region chain</a>,
-		the computed value is <a class="css" data-link-type="maybe" href="#valdef-continue-next">next</a>
+		the computed value is <a class="css" data-link-type="maybe" href="#valdef-continue-auto">auto</a>
 
       <li>On a page
 		the computed value is <a class="css" data-link-type="maybe" href="#valdef-continue-paginate">paginate</a>
@@ -1547,9 +1549,9 @@ <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno
 </ol>
 
 
-   <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,
-we would need to specify that next computes to next on it,
-or introduce a new value and have next compute to that
+   <p class="issue" id="issue-53644667"><a class="self-link" href="#issue-53644667"></a>If we introduce a pseudo element that can select columns in a multicol,
+we would need to specify that auto computes to auto on it,
+or introduce a new value and have auto compute to that
 (but what would that value compute to on things that aren’t columns?).</p>
 
 
@@ -1570,9 +1572,9 @@ <h2 class="heading settled" data-level="5" id="paginated-overflow"><span class="
    <p class="issue" id="issue-338ad0f3"><a class="self-link" href="#issue-338ad0f3"></a>Pages should be possible to style with @page rules. How does that work for nested pages?</p>
 
 
-   <div class="issue" id="issue-0cd83080"><a class="self-link" href="#issue-0cd83080"></a>
+   <div class="issue" id="issue-67ad77e5"><a class="self-link" href="#issue-67ad77e5"></a>
 Should traditional pagination (e.g. when printing)
-be expressed through some magic in the computed value of <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: next</a>,
+be expressed through some magic in the computed value of <a class="css" data-link-type="maybe" href="#valdef-continue-auto">auto</a>,
 or by inserting this in the UA stylesheet:
 
     <pre><code class="lang-css">@media (overflow-block: paged), (overflow-block: optional-paged) {
@@ -2466,7 +2468,11 @@ <h3 class="no-num heading settled" id="index-defined-here"><span class="content"
   <ul class="indexlist">
    <li>3d-preserving child, <a href="#3d_preserving-child">2.2</a>
    <li>3d-preserving descendant, <a href="#3d_preserving-descendant">2.2</a>
-   <li>auto, <a href="#valdef-overflow-auto">3</a>
+   <li>auto
+    <ul>
+     <li>value for overflow, <a href="#valdef-overflow-auto">3</a>
+     <li>value for continue, <a href="#valdef-continue-auto">4</a>
+    </ul>
    <li>border-box overflow, <a href="#border_box-overflow">2.3</a>
    <li>border-box overflow rectangle, <a href="#border_box-overflow-rectangle">2.3</a>
    <li>border-box overflow region, <a href="#border_box-overflow-region">2.3</a>
@@ -2480,7 +2486,6 @@ <h3 class="no-num heading settled" id="index-defined-here"><span class="content"
    <li>ink overflow region, <a href="#ink-overflow-region">2.1</a>
    <li>&lt;integer>, <a href="#valdef-max-lines-integer">6.2</a>
    <li>max-lines, <a href="#propdef-max-lines">6.2</a>
-   <li>next, <a href="#valdef-continue-next">4</a>
    <li>non-3d-preserving child, <a href="#non_3d_preserving-child">2.2</a>
    <li>none, <a href="#valdef-max-lines-none">6.2</a>
    <li>::nth-fragment(), <a href="#selectordef-nth-fragment">6.1.1</a>
@@ -2682,8 +2687,8 @@ <h2 class="no-num heading settled" id="property-index"><span class="content">Pro
      <td>see individual properties
     <tr>
      <th scope="row"><a class="css" data-link-type="property" href="#propdef-continue">continue</a>
-     <td>next | overflow | paginate | fragments | discard
-     <td>next
+     <td>auto | overflow | paginate | fragments | discard
+     <td>auto
      <td>block containers [CSS21], flex containers [CSS3-FLEXBOX], and grid containers [CSS3-GRID-LAYOUT]
      <td>no
      <td>N/A
@@ -2770,14 +2775,14 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
 		should this work by turning it directly into one,
 		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>
    <div class="issue">If we introduce a pseudo element that can select columns in a multicol,
-we would need to specify that next computes to next on it,
-or introduce a new value and have next compute to that
-(but what would that value compute to on things that aren’t columns?).<a href="#issue-598fb492"> ↵ </a></div>
+we would need to specify that auto computes to auto on it,
+or introduce a new value and have auto compute to that
+(but what would that value compute to on things that aren’t columns?).<a href="#issue-53644667"> ↵ </a></div>
    <div class="issue">Write this section<a href="#issue-001d5014"> ↵ </a></div>
    <div class="issue">Pages should be possible to style with @page rules. How does that work for nested pages?<a href="#issue-338ad0f3"> ↵ </a></div>
    <div class="issue">
 Should traditional pagination (e.g. when printing)
-be expressed through some magic in the computed value of <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: next</a>,
+be expressed through some magic in the computed value of <a class="css" data-link-type="maybe" href="#valdef-continue-auto">auto</a>,
 or by inserting this in the UA stylesheet:
 
     <pre><code class="lang-css">@media (overflow-block: paged), (overflow-block: optional-paged) {
@@ -2787,7 +2792,7 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
 }
 </code></pre>
 
-<a href="#issue-0cd83080"> ↵ </a>
+<a href="#issue-67ad77e5"> ↵ </a>
    </div>
    <div class="issue">Traditional pagination (e.g. when printing) assumes that
 :root is contained in the page box,