[css3-overflow] Note one issue that needs to be reworded for overflow-x and overflow-y, and specify that setting of display/position/float can't change display-inside between fragments.

Author: dbaron

css3-overflow/Overview.html

@@ -840,7 +840,13 @@ <h4 id=style-of-fragments><span class=secno>5.1.2. </span>Styling of
    href="#overflow"><code class=css>overflow</code></a>’ on the first
    fragment does not cause the <a href="#fragment-box"><i>fragment
    box</i></a> not to exist; whether there are fragment boxes at all is
-   determined by the computed value of overflow for the element.
+   determined by the computed value of overflow for the element. <span
+   class=issue>Need to reword this to refer to the appropriate choice of
+   ‘<a href="#overflow-x"><code class=css>overflow-x</code></a>’ or ‘<a
+   href="#overflow-y"><code class=css>overflow-y</code></a>’, and then
+   point to rule about the handling of the other one of ‘<a
+   href="#overflow-x"><code class=css>overflow-x</code></a>’ or ‘<a
+   href="#overflow-y"><code class=css>overflow-y</code></a>’.</span>
 
   <p> Styling an ‘<code class=css>::nth-fragment()</code>’ pseudo-element
    with the ‘<code class=property>content</code>’ property has no effect;
@@ -855,12 +861,19 @@ <h4 id=style-of-fragments><span class=secno>5.1.2. </span>Styling of
    later fragment boxes, it still counts as though it was generated. However,
    since it is not generated, it does not contain any content.
 
-  <p class=issue> Would it make more sense to forbid ‘<code
-   class=css>display:none</code>’? Or perhaps to forbid ‘<code
-   class=property>display</code>’, ‘<code
-   class=property>position</code>’, ‘<code
-   class=property>float</code>’, and similar (in addition to ‘<a
-   href="#overflow"><code class=property>overflow</code></a>’)?
+  <p> Specifying other values of ‘<code class=property>display</code>’,
+   ‘<code class=property>position</code>’, or ‘<code
+   class=property>float</code>’ is permitted, but is not allowed to change
+   the computed value of ‘<code class=property>display-inside</code>’.
+   (Since ‘<a href="#overflow"><code class=property>overflow</code></a>’,
+   ‘<a href="#overflow-x"><code class=property>overflow-x</code></a>’,
+   and ‘<a href="#overflow-y"><code class=property>overflow-y</code></a>’
+   only apply to block containers and flex containers, the computed value of
+   ‘<code class=property>display-inside</code>’ is always ‘<code
+   class=css>block</code>’ or ‘<code class=css>flex</code>’. <span
+   class=issue>Need to specify exactly how this works, but it depends on
+   having ‘<code class=property>display-inside</code>’ and ‘<code
+   class=property>display-outside</code>’ specified.</span>
 
   <p> To match the model for other pseudo-elements where the pseudo-elements
    live inside their corresponding element, declarations in ‘<code

css3-overflow/Overview.src.html

@@ -642,6 +642,10 @@ <h4 id="style-of-fragments">Styling of fragments</h4>
 		does not cause the <i>fragment box</i> not to exist;
 		whether there are fragment boxes at all is determined by
 		the computed value of overflow for the element.
+		<span class="issue">Need to reword this to refer to the
+		appropriate choice of ''overflow-x'' or ''overflow-y'',
+		and then point to rule about the handling of the other one
+		of ''overflow-x'' or ''overflow-y''.</span>
 	</p>
 
 	<p>
@@ -661,10 +665,17 @@ <h4 id="style-of-fragments">Styling of fragments</h4>
 		However, since it is not generated, it does not contain any content.
 	</p>
 
-	<p class="issue">
-		Would it make more sense to forbid ''display:none''?
-		Or perhaps to forbid 'display', 'position', 'float',
-		and similar (in addition to 'overflow')?
+	<p>
+		Specifying other values of 'display', 'position',
+		or 'float' is permitted, but is not allowed to change
+		the computed value of 'display-inside'.
+		(Since 'overflow', 'overflow-x', and 'overflow-y' only
+		apply to block containers and flex containers,
+		the computed value of 'display-inside' is always
+		''block'' or ''flex''.
+		<span class="issue">Need to specify exactly how this works,
+		but it depends on
+		having 'display-inside' and 'display-outside' specified.</span>
 	</p>
 
 	<p>