w3c
diff --git a/‎css-overflow/Overview.bs‎
Lines changed: 48 additions & 27 deletions b/‎css-overflow/Overview.bs‎
Lines changed: 48 additions & 27 deletions
@@ -466,10 +466,19 @@ Introduction</h2>
 
 <h2 id="fragmentation">Fragmentation of overflow</h2>
 
+The 'continue' property gives authors the ability
+to request that content that does not fit inside an element
+be fragmented (in the sense of [[!CSS3-BREAK]]),
+and provides alternatives
+for where the remaining content should continue.
+
+Notably, this property explains traditional pagination,
+and extends it further.
+
 	<pre class=propdef>
 		Name: continue
-		Value: ''auto'' | ''overflow'' | ''paginate'' | ''fragments'' | ''discard'' | ''next'' 
-		Initial: ''auto''
+		Value: ''next'' | ''overflow'' | ''paginate'' | ''fragments'' | ''discard''
+		Initial: next
 		Applies to: block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
 		Inherited: no
 		Percentages: N/A
@@ -479,21 +488,19 @@ Introduction</h2>
 		Canonical order: <abbr title="follows order of property value definition">per grammar</abbr>
 	</pre>
 
-Issue: Naming is preliminary.
-This was initially proposed as
-"fragmentation: auto | none | break | clone | page"
-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>
 
 Note: ''continue: fragments'' replaces "overflow:fragments"
 from earlier versions of this specification,
 while ''continue: paginate'' replaces "overflow: paged-x | paged-y | paged-x-controls | paged-y-controls"
 
-Issue: The definitions below are vaguely worded, and need to be more specific.
-
 	<dl dfn-for="continue" dfn-type="value">
-		<dt><dfn>auto</dfn>
-		<dd>Behavior varies between the other values, depending on contex.
-		See the section below on computed values for details.
+		<dt><dfn>next</dfn>
+		<dd>Content that doesn't fit is pushed to the next region
+		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.
 
 		<dt><dfn>overflow</dfn>
 		<dd>Content that doesn't fit overflows, according to the 'overflow' property
@@ -502,36 +509,50 @@ Issue: The definitions below are vaguely worded, and need to be more specific.
 		<dd>Content that doesn't fit is discarded at a fragmentation break
 
 		Note: generalized from region-fragment: break; on the last region of a region chain
-		<dt><dfn>next</dfn>
-		<dd>Content that doesn't fit is pushed to the next region
-		if the element is part of a region chain,
-		or to the next page if the element is part of a page chain. If
-		there isn't a next region or page, it overflows.
 
-		Note: Behavior could have been to discard
-		but discarding anything should be a very explicit behavior
+		Issue: When the element isn't a <a spec="css-break">fragmentation container</a> already,
+		should this work by turning it directly into one,
+		or by creating a <a>fragment box</a> inside it like ''continue/fragments'' does?
 
 		<dt><dfn>paginate</dfn>
 		<dd>Content that doesn't fit paginates.
 		This creates a paginated view inside the element
 		similar to the way that 'overflow: scroll' creates a scrollable view.
 
-		Pages can be styled with @page rules.
+		See <a href="#paginated-overflow">paginated overflow</a>
 
 		Note: Print is effectively "continue: paginate" on the root.
-
-		See <a href="#paginated-overflow">paginated overflow</a>
 		<dt><dfn>fragments</dfn>
 		<dd>content that doesn't fit causes the element to copy itself and continue laying out.
+
 		See <a href="#fragment-overflow">fragment overflow</a>.
 	</dl>
 
-Issue: There is some overlap between overflow, discard and next.
-Only 2 of the 3 ever make sense in any situation,
-even though it isn't always the same two.
-It may be possible to reduce this to 2 values.
-An earlier proposal combined discard and next into break,
-although this had the downside of making discard a non explicit behavior.
+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''
+	<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''
+		<li>On a page
+		the computed value is ''continue/paginate''
+		<li>On a <a>fragment box</a>
+		the computed value is ''continue/fragments''
+		<li>Otherwise, the computed value is 'continue/overflow''
+	</ol>
+	<li>If the specified value is ''continue/framgents''
+	<ol>
+		<li>On a page
+		the computed value is ''continue/paginate''
+		<li>Otherwise, the computed value is the specified value
+	</ol>
+	<li>In all other cases, the computed value is the specified value
+</
666F
ol>
+
+Issue: The naming of this property and its values is preliminary.
+This was initially proposed as
+"fragmentation: auto | none | break | clone | page"
+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>.
 
 Note: For background discussions leading to this property, see these threads:
 <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