- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 26 Jan 2012 23:33:02 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-flexbox
In directory hutz:/tmp/cvs-serv25308
Modified Files:
Overview.html
Log Message:
Turn the layout algorithm sketch into a note.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-flexbox/Overview.html,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -d -r1.113 -r1.114
--- Overview.html 26 Jan 2012 23:32:35 -0000 1.113
+++ Overview.html 26 Jan 2012 23:33:00 -0000 1.114
@@ -1747,9 +1747,10 @@
algorithms they wish, but must produce the same results as the algorithms
described here.
- <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 ‘<a
@@ -1787,13 +1788,6 @@
<li>Align the lines, per ‘<a href="#flex-line-pack0"><code
class=property>flex-line-pack</code></a>’.
</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 ‘<code
- class=css>auto</code>’ 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
Received on Thursday, 26 January 2012 23:33:14 UTC