[css-overflow-3] Account for discarded content in min-content/max-content inline sizes (to be consistent with fragmentation in general).

Author: fantasai

css-overflow-3/Overview.bs

@@ -504,11 +504,16 @@ Limiting Visible Lines: the 'max-lines' property</h2>
 			(which is the case if the box became a <a>fragmentation container</a>
 			merely as a consequence of applying the 'max-lines' property),
 			the rest of the <a>fragmented flow</a> is discarded,
-			as if it were ''display: none'':
+			similar to if it were ''display: none'':
 			it is neither rendered,
 			nor measured as part of the box’s contents for the purpose of
-			finding its <a lt="min-content size">min-content</a> and <a>max-content sizes</a>,
+			finding its <a lt="min-content block size">min-content</a> and <a>max-content</a> <a>block sizes</a>,
 			nor does allow user interaction.
+			However, since intrinsic sizes are calculated across all <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]]).
 
 			Note: In the case of <a href="https://www.w3.org/TR/css-break-3/#parallel-flows">parallel fragmentation flows</a>,
 			content occuring after the <a>fragmentation break</a> in the box tree