- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 27 Jan 2012 01:49:46 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-flexbox
In directory hutz:/tmp/cvs-serv5264
Modified Files:
Overview.html Overview.src.html
Log Message:
Move the note about fixup order from the layout algorithm to the flexbox item section, and turned it into normative criteria.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-flexbox/Overview.html,v
retrieving revision 1.118
retrieving revision 1.119
diff -u -d -r1.118 -r1.119
--- Overview.html 27 Jan 2012 01:22:32 -0000 1.118
+++ Overview.html 27 Jan 2012 01:49:44 -0000 1.119
@@ -531,9 +531,22 @@
<li>Atomic inline-level children of flexbox
<li>Contiguous run of non-replaced inline children, wrapped into an
- anonymous block
+ anonymous box
</ol>
+ <p>Some values of ‘<code class=property>display</code>’ trigger
+ "fixup" to ensure a sensible tree structure. For example, a lone
+ ‘<code class=css>table-cell</code>’ box is fixed up by
+ generating ‘<code class=css>table</code>’, ‘<code
+ class=css>table-row-group</code>’, and ‘<code
+ class=css>table-row</code>’ boxes around it. This fixup must occur
+ <em>before</em> a flexbox's contents are checked to see if it's necessary
+ to generate anonymous flexbox items.
+
+ <p class=note>In the future, other kinds of fixup such as ‘<code
+ class=css>display:run-in</code>’ or ‘<code
+ class=css>display:ruby</code>’ should also run before flexbox fixup.
+
<div class=example>
<p>Examples of flexbox items:</p>
@@ -1821,24 +1834,15 @@
<p>To lay out a flexbox and its contents, follow these steps:
<ol>
- <li>
- <p>Re-order the flexbox items according to their ‘<a
- href="#flex-order0"><code class=property>flex-order</code></a>’.
- The items with the lowest (most negative) ‘<a
- href="#flex-order0"><code class=property>flex-order</code></a>’
- values are first in the ordering. If multiple items share a ‘<a
- href="#flex-order0"><code class=property>flex-order</code></a>’
- value, they're ordered by document order. This affects the order in
- which the flexbox items generate boxes in the box-tree, and how the rest
- of this algorithm deals with the items.</p>
-
- <p class=note>Note that some types of box-tree fixup, such as wrapping
- anonymous table boxes around bare table-cell boxes, occur before flexbox
- items are even determined, so ‘<a href="#flex-order0"><code
- class=property>flex-order</code></a>’ has no effect on these.</p>
-
- <p class=issue>Are there any other types of box-tree fixup that occur
- that I need to worry about? Maybe Ruby?</p>
+ <li>Re-order the flexbox items according to their ‘<a
+ href="#flex-order0"><code class=property>flex-order</code></a>’.
+ The items with the lowest (most negative) ‘<a
+ href="#flex-order0"><code class=property>flex-order</code></a>’
+ values are first in the ordering. If multiple items share a ‘<a
+ href="#flex-order0"><code class=property>flex-order</code></a>’
+ value, they're ordered by document order. This affects the order in which
+ the flexbox items generate boxes in the box-tree, and how the rest of
+ this algorithm deals with the items.
<li>
<p>Resolve the width and height of every flexbox item into an absolute
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-flexbox/Overview.src.html,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- Overview.src.html 27 Jan 2012 01:22:32 -0000 1.117
+++ Overview.src.html 27 Jan 2012 01:49:44 -0000 1.118
@@ -186,9 +186,13 @@
<li>Atomic inline-level children of flexbox</li>
- <li>Contiguous run of non-replaced inline children, wrapped into an anonymous block</li>
+ <li>Contiguous run of non-replaced inline children, wrapped into an anonymous box</li>
</ol>
+ <p>Some values of 'display' trigger "fixup" to ensure a sensible tree structure. For example, a lone ''table-cell'' box is fixed up by generating ''table'', ''table-row-group'', and ''table-row'' boxes around it. This fixup must occur <em>before</em> a flexbox's contents are checked to see if it's necessary to generate anonymous flexbox items.</p>
+
+ <p class='note'>In the future, other kinds of fixup such as ''display:run-in'' or ''display:ruby'' should also run before flexbox fixup.</p>
+
<div class="example">
<p>Examples of flexbox items:</p>
<pre>
@@ -878,13 +882,7 @@
<p>To lay out a flexbox and its contents, follow these steps:</p>
<ol>
- <li>
- <p>Re-order the flexbox items according to their 'flex-order'. The items with the lowest (most negative) 'flex-order' values are first in the ordering. If multiple items share a 'flex-order' value, they're ordered by document order. This affects the order in which the flexbox items generate boxes in the box-tree, and how the rest of this algorithm deals with the items.</p>
-
- <p class='note'>Note that some types of box-tree fixup, such as wrapping anonymous table boxes around bare table-cell boxes, occur before flexbox items are even determined, so 'flex-order' has no effect on these.</p>
-
- <p class='issue'>Are there any other types of box-tree fixup that occur that I need to worry about? Maybe Ruby?</p>
- </li>
+ <li>Re-order the flexbox items according to their 'flex-order'. The items with the lowest (most negative) 'flex-order' values are first in the ordering. If multiple items share a 'flex-order' value, they're ordered by document order. This affects the order in which the flexbox items generate boxes in the box-tree, and how the rest of this algorithm deals with the items.</li>
<li>
<p>Resolve the width and height of every flexbox item into an absolute length. If the width or height is already an absolute length (like ''50px'') or was transformed into an absolute length at computed-value time (like ''10em''), skip the rest of this step for that dimension.</p>
Received on Friday, 27 January 2012 01:49:47 UTC