Mercurial > drafts / changeset

     1.1 --- a/css3-overflow/Overview.html	Mon Mar 25 16:15:28 2013 -0700
     1.2 +++ b/css3-overflow/Overview.html	Mon Mar 25 16:22:51 2013 -0700
     1.3 @@ -840,7 +840,13 @@
     1.4     href="#overflow"><code class=css>overflow</code></a>’ on the first
     1.5     fragment does not cause the <a href="#fragment-box"><i>fragment
     1.6     box</i></a> not to exist; whether there are fragment boxes at all is
     1.7 -   determined by the computed value of overflow for the element.
     1.8 +   determined by the computed value of overflow for the element. <span
     1.9 +   class=issue>Need to reword this to refer to the appropriate choice of
    1.10 +   ‘<a href="#overflow-x"><code class=css>overflow-x</code></a>’ or ‘<a
    1.11 +   href="#overflow-y"><code class=css>overflow-y</code></a>’, and then
    1.12 +   point to rule about the handling of the other one of ‘<a
    1.13 +   href="#overflow-x"><code class=css>overflow-x</code></a>’ or ‘<a
    1.14 +   href="#overflow-y"><code class=css>overflow-y</code></a>’.</span>
    1.15  
    1.16    <p> Styling an ‘<code class=css>::nth-fragment()</code>’ pseudo-element
    1.17     with the ‘<code class=property>content</code>’ property has no effect;
    1.18 @@ -855,12 +861,19 @@
    1.19     later fragment boxes, it still counts as though it was generated. However,
    1.20     since it is not generated, it does not contain any content.
    1.21  
    1.22 -  <p class=issue> Would it make more sense to forbid ‘<code
    1.23 -   class=css>display:none</code>’? Or perhaps to forbid ‘<code
    1.24 -   class=property>display</code>’, ‘<code
    1.25 -   class=property>position</code>’, ‘<code
    1.26 -   class=property>float</code>’, and similar (in addition to ‘<a
    1.27 -   href="#overflow"><code class=property>overflow</code></a>’)?
    1.28 +  <p> Specifying other values of ‘<code class=property>display</code>’,
    1.29 +   ‘<code class=property>position</code>’, or ‘<code
    1.30 +   class=property>float</code>’ is permitted, but is not allowed to change
    1.31 +   the computed value of ‘<code class=property>display-inside</code>’.
    1.32 +   (Since ‘<a href="#overflow"><code class=property>overflow</code></a>’,
    1.33 +   ‘<a href="#overflow-x"><code class=property>overflow-x</code></a>’,
    1.34 +   and ‘<a href="#overflow-y"><code class=property>overflow-y</code></a>’
    1.35 +   only apply to block containers and flex containers, the computed value of
    1.36 +   ‘<code class=property>display-inside</code>’ is always ‘<code
    1.37 +   class=css>block</code>’ or ‘<code class=css>flex</code>’. <span
    1.38 +   class=issue>Need to specify exactly how this works, but it depends on
    1.39 +   having ‘<code class=property>display-inside</code>’ and ‘<code
    1.40 +   class=property>display-outside</code>’ specified.</span>
    1.41  
    1.42    <p> To match the model for other pseudo-elements where the pseudo-elements
    1.43     live inside their corresponding element, declarations in ‘<code

     2.1 --- a/css3-overflow/Overview.src.html	Mon Mar 25 16:15:28 2013 -0700
     2.2 +++ b/css3-overflow/Overview.src.html	Mon Mar 25 16:22:51 2013 -0700
     2.3 @@ -642,6 +642,10 @@
     2.4  		does not cause the <i>fragment box</i> not to exist;
     2.5  		whether there are fragment boxes at all is determined by
     2.6  		the computed value of overflow for the element.
     2.7 +		<span class="issue">Need to reword this to refer to the
     2.8 +		appropriate choice of ''overflow-x'' or ''overflow-y'',
     2.9 +		and then point to rule about the handling of the other one
    2.10 +		of ''overflow-x'' or ''overflow-y''.</span>
    2.11  	</p>
    2.12  
    2.13  	<p>
    2.14 @@ -661,10 +665,17 @@
    2.15  		However, since it is not generated, it does not contain any content.
    2.16  	</p>
    2.17  
    2.18 -	<p class="issue">
    2.19 -		Would it make more sense to forbid ''display:none''?
    2.20 -		Or perhaps to forbid 'display', 'position', 'float',
    2.21 -		and similar (in addition to 'overflow')?
    2.22 +	<p>
    2.23 +		Specifying other values of 'display', 'position',
    2.24 +		or 'float' is permitted, but is not allowed to change
    2.25 +		the computed value of 'display-inside'.
    2.26 +		(Since 'overflow', 'overflow-x', and 'overflow-y' only
    2.27 +		apply to block containers and flex containers,
    2.28 +		the computed value of 'display-inside' is always
    2.29 +		''block'' or ''flex''.
    2.30 +		<span class="issue">Need to specify exactly how this works,
    2.31 +		but it depends on
    2.32 +		having 'display-inside' and 'display-outside' specified.</span>
    2.33  	</p>
    2.34  
    2.35  	<p>