W3C home > Mailing lists > Public > public-css-commits@w3.org > January 2012

csswg/css3-flexbox Overview.html,1.108,1.109 Overview.src.html,1.108,1.109

From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 25 Jan 2012 23:06:20 +0000
To: public-css-commits@w3.org
Message-Id: <E1RqBv2-0004Am-5h@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-flexbox
In directory hutz:/tmp/cvs-serv16026

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Fix issue about table-fixup happening before flex-order, and refine issue to a more general question about box fixup.

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-flexbox/Overview.html,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -d -r1.108 -r1.109
--- Overview.html	25 Jan 2012 23:02:53 -0000	1.108
+++ Overview.html	25 Jan 2012 23:06:18 -0000	1.109
@@ -1818,17 +1818,24 @@
   <p>To lay out a flexbox and its contents, follow these steps:
 
   <ol>
-   <li>Re-order the flexbox items according to their &lsquo;<a
-    href="#flex-order0"><code class=property>flex-order</code></a>&rsquo;.
-    The items with the lowest (most negative) &lsquo;<a
-    href="#flex-order0"><code class=property>flex-order</code></a>&rsquo;
-    values are first in the ordering. If multiple items share a &lsquo;<a
-    href="#flex-order0"><code class=property>flex-order</code></a>&rsquo;
-    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 class=issue>When, precisely, should this happen? For example, should
-     table-fixup among the children happen before this?
+   <li>
+    <p>Re-order the flexbox items according to their &lsquo;<a
+     href="#flex-order0"><code class=property>flex-order</code></a>&rsquo;.
+     The items with the lowest (most negative) &lsquo;<a
+     href="#flex-order0"><code class=property>flex-order</code></a>&rsquo;
+     values are first in the ordering. If multiple items share a &lsquo;<a
+     href="#flex-order0"><code class=property>flex-order</code></a>&rsquo;
+     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 &lsquo;<a href="#flex-order0"><code
+     class=property>flex-order</code></a>&rsquo; 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>
     <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.108
retrieving revision 1.109
diff -u -d -r1.108 -r1.109
--- Overview.src.html	25 Jan 2012 23:02:53 -0000	1.108
+++ Overview.src.html	25 Jan 2012 23:06:18 -0000	1.109
@@ -882,9 +882,12 @@
 	<p>To lay out a flexbox and its contents, follow these steps:</p>
 
 	<ol>
-		<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>
+			<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='issue'>When, precisely, should this happen?  For example, should table-fixup among the children happen before this?
+			<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>
Received on Wednesday, 25 January 2012 23:06:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:26:09 UTC