- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 30 Jan 2012 21:03:35 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-flexbox In directory hutz:/tmp/cvs-serv596 Modified Files: Overview.html Overview.src.html Log Message: Change multicol to simply have no effect, rather than computing to initial values. Index: Overview.html =================================================================== RCS file: /sources/public/csswg/css3-flexbox/Overview.html,v retrieving revision 1.126 retrieving revision 1.127 diff -u -d -r1.126 -r1.127 --- Overview.html 30 Jan 2012 18:12:44 -0000 1.126 +++ Overview.html 30 Jan 2012 21:03:33 -0000 1.127 @@ -478,10 +478,7 @@ <ul> <li>all of the ‘<code class=css>column-*</code>’ properties in - the Multicol module compute to their initial values on a flexbox - (‘<code class=property>break-before</code>’, ‘<code - class=property>break-inside</code>’, and ‘<code - class=property>break-after</code>’ are still valid on a flexbox). + the Multicol module have no effect on a flexbox. <li>‘<code class=property>float</code>’ and ‘<code class=property>clear</code>’ have no effect on a flexbox item. Index: Overview.src.html =================================================================== RCS file: /sources/public/csswg/css3-flexbox/Overview.src.html,v retrieving revision 1.124 retrieving revision 1.125 diff -u -d -r1.124 -r1.125 --- Overview.src.html 30 Jan 2012 18:12:44 -0000 1.124 +++ Overview.src.html 30 Jan 2012 21:03:33 -0000 1.125 @@ -161,7 +161,7 @@ <p>Flexboxes use a new layout algorithm, and so some properties that were designed with the assumption of block layout don't make sense in a flexbox context. In particular:</p> <ul> - <li>all of the 'column-*' properties in the Multicol module compute to their initial values on a flexbox ('break-before', 'break-inside', and 'break-after' are still valid on a flexbox).</li> + <li>all of the 'column-*' properties in the Multicol module have no effect on a flexbox.</li> <li>'float' and 'clear' have no effect on a flexbox item. Using 'float' on an element still causes that element's 'display' property to compute to ''block'', as normal, because that occurs before flexbox items are determined (the algorithm for wrapping children of a flexbox into <i>flexbox items</i> needs the computed value of 'display').</li>
Received on Monday, 30 January 2012 21:03:36 UTC