Tue, 27 Mar 2012 14:04:00 -0700
Changed paragraph on pseudo-elements to disallow 'flow-into' on all pseudo-elements because moving a '::before' element (for a example) to a named flow does not seem useful and causes specification and implementation complexity.
css3-regions/Overview.html | file | annotate | diff | comparison | revisions | |
css3-regions/Overview.src.html | file | annotate | diff | comparison | revisions |
1.1 --- a/css3-regions/Overview.html Tue Mar 27 14:00:37 2012 -0700 1.2 +++ b/css3-regions/Overview.html Tue Mar 27 14:04:00 2012 -0700 1.3 @@ -859,7 +859,14 @@ 1.4 <tr> 1.5 <th>Applies to: 1.6 1.7 - <td>any element 1.8 + <td>any element. 1.9 + <p>The ‘<a href="#flow-into"><code 1.10 + class=property>flow-into</code></a>’ property does not apply to 1.11 + any <a 1.12 + href="http://www.w3.org/TR/selectors/#pseudo-elements">pseudo-element</a> 1.13 + such as <code class=css>::first-line</code>, <code 1.14 + class=css>::first-letter</code>, <code class=css>::before</code> or 1.15 + <code class=css>::after</code>. 1.16 1.17 <tr> 1.18 <th>Inherited: 1.19 @@ -993,17 +1000,6 @@ 1.20 unintended results.</p> 1.21 </div> 1.22 1.23 - <p>The ‘<a href="#flow-into"><code 1.24 - class=property>flow-into</code></a>’ property does not apply to the 1.25 - <code class=css>::first-line</code> and <code 1.26 - class=css>::first-letter</code> pseudo-elements. 1.27 - 1.28 - <p>The effect of ‘<a href="#flow-into"><code 1.29 - class=property>flow-into</code></a>’ on generated content such as 1.30 - <code class=css>::marker</code>, <code class=css>::before</code> and <code 1.31 - class=css>::after</code> is undefined. This may change depending on 1.32 - implementation feedback. 1.33 - 1.34 <h3 id=the-flow-from-property><span class=secno>4.2. </span>The ‘<a 1.35 href="#flow-from"><code class=property>flow-from</code></a>’ 1.36 property</h3> 1.37 @@ -2461,6 +2457,13 @@ 1.38 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15938">Issue 1.39 15938</a> and required in the general effort to have the DOM APIs work 1.40 with non-element regions. 1.41 + 1.42 + <li>Changed paragraph on pseudo-elements to disallow ‘<a 1.43 + href="#flow-into"><code class=property>flow-into</code></a>’ on all 1.44 + pseudo-elements because moving a ‘<code 1.45 + class=css>::before</code>’ element (for a example) to a named flow 1.46 + does not seem useful and causes specification and implementation 1.47 + complexity. 1.48 </ul> 1.49 1.50 <h3 id="changes_from_June_09_2011"><span class=secno>11.2. </span>Changes
2.1 --- a/css3-regions/Overview.src.html Tue Mar 27 14:00:37 2012 -0700 2.2 +++ b/css3-regions/Overview.src.html Tue Mar 27 14:04:00 2012 -0700 2.3 @@ -690,7 +690,9 @@ 2.4 <tr> 2.5 <th>Applies to:</th> 2.6 2.7 - <td>any element</td> 2.8 + <td>any element. <p>The 'flow-into' property does not apply to any <a href="http://www.w3.org/TR/selectors/#pseudo-elements">pseudo-element</a> such as 2.9 + <code class="css">::first-line</code>, <code class="css">::first-letter</code>, 2.10 + <code class="css">::before</code> or <code class="css">::after</code>.</p></td> 2.11 </tr> 2.12 2.13 <tr> 2.14 @@ -800,11 +802,7 @@ 2.15 </div> 2.16 2.17 2.18 - <p>The 'flow-into' property does not apply to the <code class="css">::first-line</code> and <code class="css">::first-letter</code> pseudo-elements.</p> 2.19 2.20 - <p>The effect of 'flow-into' on generated content such as <code class="css">::marker</code>, 2.21 - <code class="css">::before</code> and <code class="css">::after</code> 2.22 - is undefined. This may change depending on implementation feedback.</p> 2.23 2.24 <h3 id="the-flow-from-property">The 'flow-from' property</h3> 2.25 2.26 @@ -2045,6 +2043,9 @@ 2.27 <li>Modified region layout event to be dispatched on <code>NamedFlow</code> instead of region 2.28 as before. Was requested by <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15938">Issue 15938</a> 2.29 and required in the general effort to have the DOM APIs work with non-element regions.</li> 2.30 + <li>Changed paragraph on pseudo-elements to disallow 'flow-into' on all pseudo-elements because 2.31 + moving a '::before' element (for a example) to a named flow does not seem useful and causes specification 2.32 + and implementation complexity.</li> 2.33 </ul> 2.34 2.35