[css-flexbox] Update Changes section. Fix up clarifications to abspos reordering.

Author: fantasai

css-flexbox/Overview.bs

@@ -663,7 +663,8 @@ Absolutely-Positioned Flex Children</h3>
 
 	In other words,
 	the <a>static position</a> of an absolutely positioned child of a <a>flex container</a>
-	is determined by setting its <a>static-position rectangle</a> to the <a>flex container's</a> content box,
+	is determined <em>after flex layout</em>
+	by setting the child’s <a>static-position rectangle</a> to the <a>flex container's</a> content box,
 	then aligning the absolutely positioned child within this rectangle
 	according to the 'justify-content' value of the <a>flex container</a>
 	and the 'align-self' value of the child itself.
@@ -1215,7 +1216,8 @@ Display Order: the 'order' property</h3>
 	</pre>
 
 	<p>
-		The 'order' property controls the order in which flex items appear within their flex container,
+		The 'order' property controls the order in which
+		children of a flex container appear within the flex container,
 		by assigning them to ordinal groups.
 		It takes a single <dfn value for=order><<integer>></dfn> value,
 		which specifies which ordinal group the <a>flex item</a> belongs to.
@@ -1250,7 +1252,7 @@ Display Order: the 'order' property</h3>
 
 	<p>
 		Unless otherwise specified by a future specification,
-		this property has no effect on boxes that are not <i>flex items</i>.
+		this property has no effect on boxes that are not children of a <a>flex container</a>.
 
 <h4 id="order-accessibility">
 Reordering and Accessibility</h4>
@@ -1721,7 +1723,6 @@ The 'flex-basis' property</h4>
 		The CSSWG is waiting for feedback from implementers on this issue.
 
 		<small><sup>1</sup> Alternate keyword suggestions welcome.</small>
-		<small><sup>1</sup> Alternate keyword suggestions welcome.</small>
 	</div>
 
 	<p>
@@ -2278,12 +2279,16 @@ Initial Setup</h3>
 			as described in the <a href="#flex-items">Flex Items</a> section.
 
 		<li id='algo-flex-order'>
-			<strong>Re-order the flex items according to their 'order'.</strong>
+			<strong>Re-order the flex items (and any absolutely positioned flex container children) according to their 'order'.</strong>
 			The flex items with the lowest (most negative) 'order' values are first in the ordering.
 			If multiple flex items share an 'order' value,
 			they're ordered by document order.
 			This effectively changes the order of their boxes in the box-tree,
 			and how the rest of this algorithm deals with the generated flex items.
+
+			Note: Absolutely-positioned children of a flex container
+			do not participate in flex layout,
+			but are reordered together with any <i>flex item</i> children.
 	</ol>
 
 <h3 id='line-sizing'>
@@ -3283,8 +3288,14 @@ Boris Zbarsky.
 <h3 id="changes-201403">
 Changes since the 25 March 2014 LCWD</h3>
 
+	This section documents the changes since the previous publication.
+	A <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325">Disposition of Comments</a> is also available.
+
+<h4 id="change-201403-substantive">
+Substantive Changes and Bugfixes</h4>
+
 	The following significant changes were made since the
-	<a href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/">25 March 2014 Last Call Working Draft</a>:
+	<a href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/">25 March 2014 Last Call Working Draft</a>
 
 	<ul>
 		<li id="change-201403-min-auto-not">
@@ -3294,7 +3305,51 @@ Changes since the 25 March 2014 LCWD</h3>
 			<a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-30">30</a>)
 
 			<blockquote>
-				On a <a>flex item</a> whose 'overflow' is <del>not</del> ''overflow/visible'',
+				On a <a>flex item</a> whose 'overflow' is <del>not</del> ''overflow/visible'' <ins>in the <i>main axis</i></ins>,
+			</blockquote>
+
+		<li id="change-201403-min-auto-ratio">
+			Expanded and rewrote definition of ''min-height/min-width: auto''
+			to add special handling of items with intrinsic ratios.
+			(Issues <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-16">16</a>
+			and <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-28">28</a>)
+
+			<blockquote>
+				<p>On a <a>flex item</a> whose 'overflow' is not ''overflow/visible'',
+				<ins>the following table gives the minimum size:
+				<a href="#valdef-min-width-min-height-auto"><strong>[see table]</strong></a></ins><br>
+				<del>this keyword specifies as the minimum size the smaller of:</del>
+				<del>
+					<ul>
+						<li>the <a>min-content size</a>, or
+						<li>the computed 'width'/'height', if that value is <a>definite</a>.
+					</ul>
+				</del>
+			</blockquote>
+
+		<li id="change-201403-min-auto-main-size-basis">
+			Adjusted ''min-height/min-width: auto''
+			to only apply the computed main size as a minimum
+			in cases where the flex basis was retrieved from the main size property.
+			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-19">19</a>)
+
+			<blockquote>
+				<p>&hellip; is defined if <ins>the item’s flex-basis is ''main-size'' and</ins>
+				its computed main size property is definite &hellip;
+			</blockquote>
+
+		<li id="change-201403-min-auto-intrinsic-percentages">
+			Defined that any size adjustment imposed by a box’s ''min-height/min-width: auto''
+			is not consulted when percentage-sizing any of its contents.
+			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-27">27</a>)
+			<blockquote>
+				<p>In order to prevent cycling sizing,
+				the ''auto'' value of 'min-height' and 'max-height'
+				does not factor into the percentage size resolution of the box’s contents.
+				For example, a percentage-height block whose flex item parent has
+				''height: 120em; min-height: auto''
+				will size itself against ''height: 120em'' regardless of the impact
+				that 'min-height' might have on the used size of the flex item.
 			</blockquote>
 
 		<li id="change-201403-flex-basis-auto">
@@ -3303,34 +3358,36 @@ Changes since the 25 March 2014 LCWD</h3>
 			could each be explicitly specified.
 			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-20">20</a>)
 
-		<li id="change-201403-css21-staticpos">
-			Clarified how the static position of an absolutely-positioned child of a flex container
-			is calculated by introducing an explanation of the effect more closely tied
-			with CSS2.1 concepts and terminology.
-			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-12">12</a>)
+			Note: This change is open for feedback from implementers,
+			and an alternative solution is also described if the current one is deemed unworkable.
 
-			Issue: Insert diff.
-
-		<li id="change-201403-clarify-stretched">
-			Clarified what a <i>stretched</i> flex item is
-			for the purposes of special behavior (like definiteness).
-			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-25">25</a>)
+		<li id="change-201403-definite-flexing">
+			Defined <i>flex items</i> with a <i>definite</i> <i>flex basis</i>
+			to also be <i>definite</i> in the <i>main axis</i>,
+			allowing resolution of percentage-sized children
+			even when the item itself is flexible.
+			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-26">26</a>)
 
-		<li id="change-201403-max-intrinsic">
-			Fixed <a href="#intrinsic-sizes">max-content sizing of flex containers</a>
-			to account for flexing behavior
-			by normalizing per flex fraction rather than merely summing the max-content sizes of the flex items.
-			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-39">39</a>)
+			<blockquote>
+				<p>If a percentage is going to be resolved against a flex item’s main size,
+				and the flex item has a definite flex basis,
+				the main size must be treated as definite for the purpose of resolving the percentage,
+				and the percentage must resolve against the flexed main size of the flex item
+				(that is, after the layout algorithm below has been completed for the flex item’s flex container,
+				and the flex item has acquired its final size).
+			</blockquote>
 
 		<li id="change-201403-clamp-single-line">
 			Clamp a single line flexbox's line cross size to the container's own min/max,
 			even when the container's size is indefinite.
-			(Matches Blink's behavior.)
+			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-9">9</a>)
 
 			<blockquote>
 				<ul>
 					<li>
-						The used cross-size of the <a>flex line</a> is the largest of the numbers found in the previous two steps and zero.
+						The used cross-size of the <a>flex line</a> is
+						the largest of the numbers found in the previous two steps
+						and zero.
 
 						<p><ins>If the flex container has only one flex line
 						(even if it's a multi-line flex container),
@@ -3341,34 +3398,97 @@ Changes since the 25 March 2014 LCWD</h3>
 			</blockquote>
 
 		<li id="change-201403-resolve-flex">
-			Fixed various errors in the new Resolving Flexible Lengths section
+			Fixed various errors in the new <a href="#resolve-flexible-lengths">Resolving Flexible Lengths</a> section
+			(see <a href="#change-2012-flex-continuity">March 2014 rewrite to create continuity between ''flex: 0'' and ''flex: 1''</a>)
 			and reverted the editorial structure to match the old Candidate Recommendation.
 			(Issues <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-3">3</a>,
 			 <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-4">4</a>,
 			  <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-8">8</a>,
 			  <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-10">10</a>,
 			  <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-15">15</a>)
 
+		<li id="change-201403-max-intrinsic">
+			Fixed <a href="#intrinsic-sizes">max-content sizing of flex containers</a>
+			to account for flexing behavior
+			by normalizing per flex fraction rather than merely summing the max-content sizes of the flex items.
+			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-39">39</a>)
+
 		<li id="change-201403-flex-animation">
 			Updated 'flex' property to accept animations always,
 			now that the discontinuity between 0 and non-0 values has been <a href="#change-2012-flex-continuity">fixed</a>.
 			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-5">5</a>)
+	</ul>
 
-		<li class="issue">Further changes to list here:
-		(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-9">9</a>)
-		(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-16">16</a>)
-		(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-19">19</a>)
-		(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-26">26</a>)
-		(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-27">27</a>)
-		(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-28">28</a>)
+<h4 id="change-201403-clarify">
+Clarifications</h4>
 
-	</ul>
+	The following significant changes were made since the
+	<a href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/">25 March 2014 Last Call Working Draft</a>
 
-	A <a href="http://dev.w3.org/csswg/css3-flexbox/issues-lc-20140325/">Disposition of Comments</a> is available.
+	<ul>
+		<li id="change-201403-css21-staticpos">
+			Clarified how the static position of an absolutely-positioned child of a flex container
+			is calculated by introducing an explanation of the effect more closely tied
+			with CSS2.1 concepts and terminology.
+			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-12">12</a>)
+
+			<blockquote>
+				<p><del>Its</del> <ins>The</del> static position <ins>of an absolutely-positioned child of a flex container</ins>
+				is
+				<del>calculated by first doing full flex layout without the absolutely-positioned children,
+				then positioning each absolutely-positioned child</del>
+				<ins>determined such that the child is positioned</ins>
+				as if it were the sole flex item in the flex container,
+				assuming both the child and the flex container were fixed-size boxes of their used size.
+
+				<ins><p>In other words, the static position of an absolutely positioned child of a flex container
+				is determined <em>after flex layout</em>
+				by setting the child’s <i>static-position rectangle</i> to the flex container’s content box,
+				then aligning the absolutely positioned child within this rectangle
+				according to the 'justify-content' value of the flex container and the 'align-self' value of the child itself.
+				</ins>
+			</blockquote>
+
+		<li id="change-201403-abspos-ordering">
+			Clarified application of 'order' to absolutely-positioned children of the <i>flex container</i>:
+	
+			<blockquote>
+				<p>An absolutely-positioned child of a flex container does not participate in flex layout
+				<del>beyond the reordering step</del>.
+				<ins>However, it does participate in the reordering step (see 'order'),
+				which has an effect in their painting order.</ins>
+			</blockquote>
+
+			<blockquote>
+				<p>The order property controls the order in which <del>flex items</del>
+				<ins>children of a flex container</ins>
+				appear within their flex container&hellip;
+				<p>Unless otherwise specified by a future specification,
+				this property has no effect on boxes that are not <del>flex items</del>
+				<ins>children of a flex container</ins>.
+			</blockquote>
+
+			<blockquote>
+				<ins><p class="note">Note: Absolutely-positioned children of a flex container
+				do not participate in flex layout, but are reordered
+				together with any flex item children.</p></ins>
+			</blockquote>
+
+		<li id="change-201403-clarify-stretched">
+			Clarified what a <i>stretched</i> flex item is
+			for the purposes of special behavior (like definiteness).
+			(Issue <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325#issue-25">25</a>)
+	</ul>
 
 <h3 id="changes-2012">
 Changes since the 18 September 2012 Candidate Recommendation</h3>
 
+	This section documents the changes since the previous publication.
+	A <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-2012">Disposition of Comments</a> is also available.
+
+<h4 id="changes-2014-substantive">
+Substantive Changes and Bugfixes</h4>
+
 	The following significant changes were made since the
 	<a href="http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/">18 September 2012 Candidate Recommendation</a>:
 
@@ -3397,15 +3517,15 @@ Changes since the 18 September 2012 Candidate Recommendation</h3>
 						<del>
 							<p>When used as the value of a flex item's min main size property,
 							this keyword indicates a minimum of the min-content size,
-							to help ensure that the item is large enough to fit its contents.
+							to help ensure that the item is large enough to fit its contents.</p>
 							<p class='note'>
 								It is intended that this will compute to the ''min-content'' keyword
 								when the specification defining it ([[CSS3-SIZING]]) is sufficiently mature.
+							</p>
 						</del>
 						<ins>
 							<p>On a <a>flex item</a> whose 'overflow' is not ''overflow/visible'',
 							this keyword specifies as the minimum size the smaller of:
-
 							<ul>
 								<li>the <a>min-content size</a>, or
 								<li>the computed 'width'/'height', if that value is <a>definite</a>.
@@ -3660,6 +3780,9 @@ Changes since the 18 September 2012 Candidate Recommendation</h3>
 			with <a href="#resolve-flexible-lengths">this one</a>.
 	</ul>
 
+<h4 id="changes-2014-clarify">
+Clarifications</h4>
+
 	<p>The following significant clarifications were also made:
 	<ul>
 		<li id="clarify-2012-abspos-items">