Change multicol to simply have no effect, rather than computing to initial values.

Author: tabatkins

css3-flexbox/Overview.html

@@ -478,10 +478,7 @@ <h3 id=display-flexbox><span class=secno>2.1. </span> New values for
 
   <ul>
    <li>all of the &lsquo;<code class=css>column-*</code>&rsquo; properties in
-    the Multicol module compute to their initial values on a flexbox
-    (&lsquo;<code class=property>break-before</code>&rsquo;, &lsquo;<code
-    class=property>break-inside</code>&rsquo;, and &lsquo;<code
-    class=property>break-after</code>&rsquo; are still valid on a flexbox).
+    the Multicol module have no effect on a flexbox.
 
    <li>&lsquo;<code class=property>float</code>&rsquo; and &lsquo;<code
     class=property>clear</code>&rsquo; have no effect on a flexbox item.

css3-flexbox/Overview.src.html

@@ -161,7 +161,7 @@ <h3 id='display-flexbox'>
 	<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>