[css-overflow-3] Clarify what breaks trigger discarding of subsequent content in 'continue:discard'.

Author: fantasai

css-overflow-3/Overview.bs

@@ -1588,48 +1588,20 @@ Fragmentation of Overflow: the 'continue' property</h3>
 			that captures <a>region breaks</a>,
 			if it is not already.
 			[[!CSS-BREAK-3]]
+			Content after the first [=region break=] is not rendered (see below).
+			(If the box is a [=multi-column container=],
+			any [=overflow columns=] are also not rendered.)
 
-			The position of the first <a lt="forced break">forced</a> [=region break=]
-			(whether imposed by 'max-lines' or by another mechanism,
-			such as the 'break-before'/'break-after' properties)
-			or the position of the first [=unforced break=],
-			which ever comes sooner,
-			is treated as the end of the <a>fragmentation container</a>,
-			and the remaining content after the [=fragmentation break=] is discarded,
-			similar to if it were ''display: none'':
-			* It is not rendered
-			* Just as the content is visually hidden, it is not made available for speech rendering
-			* It does not allow user interaction
-			* Issue(2970): Make sure effects on OM are well defined
-			* [=Positioned=] elements whose static position is in the discarded content are not rendered.
-
-				Issue(2971): Are we sure about that?
-				Discussions in the <a href="https://lists.w3.org/Archives/Public/www-style/2018Jul/0030.html">Sydney F2F meeting</a>
-				seemed to generally converge on this,
-				but other possibilities were raised.
-
-			However, since intrinsic sizes are calculated across <a>fragmentation containers</a>,
-			this content <em>is</em> taken into account
-			for the purpose of finding the box’s
-			<a lt="min-content inline size">min-content</a> and <a>max-content</a> <a>inline sizes</a>
-			(see [[css-break-3#varying-size-boxes]]).
-			<a lt="min-content inline size">Min-content</a> and <a>max-content</a> <a>block sizes</a>
-			are calculated based on the content
-			from the start of the [=fragmented flow=]
-			to the first [=forced break=] if any,
-			or to the end of the [=fragmented flow=] if there is no forced break.
-
-			Note: Calculating intrinsic block sizes to the first forced <em>or unforced</em> break
-			would cause intrinsic sizes to depend on layout, which would cause circularities.
-
-			The effect on [=multi-column containers=] is to discard any [=overflow column=].
-
-			Note: In the case of <a href="https://www.w3.org/TR/css-break-3/#parallel-flows">parallel fragmentation flows</a>,
-			content occurring after the <a>fragmentation break</a> in the box tree
-			could still be rendered,
-			if it is laid out above the position
-			representing the end of this <a>fragmentation container</a>.
 
+			Note: This [=region break=] might be <a lt="forced break">forced</a>
+			(e.g. imposed by 'max-lines' or by another mechanism,
+			such as the 'break-before'/'break-after' properties)
+			or [=unforced break|unforced=]
+			(e.g. if the content would otherwise overflow this [=fragmentation container=]
+			due to its size constraints).
+			Breaks applying to other [=fragmentation contexts=]
+			(such as pagination of this box itself)
+			do not cause any content to be discarded.
 	</dl>
 
 	Note: This property does <em>not</em> cause the box to [=establish an independent formatting context=].
@@ -1674,6 +1646,36 @@ Fragmentation of Overflow: the 'continue' property</h3>
 	</figure>
 	</div>
 
+	Content that is “not rendered” due to ''continue: discard''
+	is discarded, similar to ''display: none'':
+		* It is not rendered.
+		* It is also not made available for speech rendering.
+		* It does not allow user interaction.
+		* Issue(2970): Make sure effects on OM are well defined
+		* Issue(2971): What about [=positioned=] elements whose static position is in the discarded content are not rendered?
+			See also discussions in the <a href="https://lists.w3.org/Archives/Public/www-style/2018Jul/0030.html">Sydney F2F meeting</a>.
+
+	However, since intrinsic sizes are calculated across <a>fragmentation containers</a>,
+	this content <em>is</em> taken into account
+	for the purpose of finding the box’s
+	<a lt="min-content inline size">min-content</a> and <a>max-content</a> <a>inline sizes</a>
+	(see [[css-break-3#varying-size-boxes]]).
+	<a lt="min-content inline size">Min-content</a> and <a>max-content</a> <a>block sizes</a>
+	are calculated based on the content
+	from the start of the [=fragmented flow=]
+	to the first [=forced break=] if any,
+	or to the end of the [=fragmented flow=] if there is no forced break.
+
+<!--
+	Calculating intrinsic block sizes to the first forced <em>or unforced</em> break
+	would cause intrinsic sizes to depend on layout, which would cause circularities.
+-->
+
+	Note: In the case of <a href="https://www.w3.org/TR/css-break-3/#parallel-flows">parallel fragmentation flows</a>,
+	content occurring after the <a>fragmentation break</a> in the box tree
+	could still be rendered,
+	if it is laid out above the position
+	representing the end of this <a>fragmentation container</a>.
 
 <h2 class="no-num non-normative" id="priv-sec">Appendix A. Privacy and Security Considerations</h2>
 ===============================================