- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 26 Jan 2012 23:32:38 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-flexbox
In directory hutz:/tmp/cvs-serv25267
Modified Files:
Overview.html Overview.src.html
Log Message:
Tweak the wording of the issue in the layout algorithm.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-flexbox/Overview.html,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -d -r1.112 -r1.113
--- Overview.html 26 Jan 2012 23:26:32 -0000 1.112
+++ Overview.html 26 Jan 2012 23:32:35 -0000 1.113
@@ -2009,8 +2009,9 @@
item is the item's preferred size.
</ol>
- <p class=issue>I'm pretty sure the previous algorithm will eventually
- terminate. I'm not absolutely certain, though. Help?
+ <p class=issue>I'm pretty sure the previous algorithm is guaranteed to
+ terminate. I'm not absolutely certain, though. Help? (It's clear that in
+ practice, it will almost always terminate in one or two iterations.)
<p>To <dfn id=distribute-the-free-space>distribute the free space</dfn> in
a flexbox line:
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-flexbox/Overview.src.html,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -d -r1.112 -r1.113
--- Overview.src.html 26 Jan 2012 23:26:32 -0000 1.112
+++ Overview.src.html 26 Jan 2012 23:32:36 -0000 1.113
@@ -845,8 +845,8 @@
<p>This section contains normative algorithms detailing the exact layout behavior of a flexbox and its contents. The algorithms here were designed to optimize readability and theoretical simplicity, and may not necessarily be the most efficient. Implementations may use whatever actual algorithms they wish, but must produce the same results as the algorithms described here.</p>
- <div class=issue>
- <p>Here I'll outline the general structure of the layout algorithm, before I go into the ugly details below.</p>
+ <div class=note>
+ <p>This note will outline the general structure of the layout algorithm, before I go into the ugly details below, to aid in reading the relatively-long and complex algorithm.</p>
<ol>
<li>Reorder flexbox items according to 'flex-order'.</li>
@@ -871,8 +871,6 @@
<li>Align the lines, per 'flex-line-pack'.</li>
</ol>
-
- <p>Note that if any "hypothetical" size is a definite length or percentage, it's actually a real size immediately and won't change (well, aside from flexing). The hypothetical calculations are meant to give intermediate results in the presence of ''auto'' values (and others?), so I can do other calculations that depend on those lengths.</p>
</div>
<p>The layout algorithm for flexbox is, unfortunately, too complex and interdependent to usefully describe in pieces within each property's description. As such, the normative layout algorithm is described in this chapter. Note that this is the <em>definitive</em> description of the flexbox layout algorithm - any information located elsewhere in this spec is informative only. Note as well that only the <strong>output</strong> of the algorithm is normative. The precise steps described in this section are informative, and written with an eye toward clarity and simplicity, not efficiency. Any algorithm that achieves the same results is acceptable.</p>
@@ -974,7 +972,7 @@
<li>Otherwise, the used value of the main size property of every flexible item is the item's preferred size.</li>
</ol>
- <p class='issue'>I'm pretty sure the previous algorithm will eventually terminate. I'm not absolutely certain, though. Help?
+ <p class='issue'>I'm pretty sure the previous algorithm is guaranteed to terminate. I'm not absolutely certain, though. Help? (It's clear that in practice, it will almost always terminate in one or two iterations.)</p>
<p>To <dfn>distribute the free space</dfn> in a flexbox line:</p>
Received on Thursday, 26 January 2012 23:32:39 UTC