[css-flexbox] Update DoC, date, and switch to ED styling

Author: fantasai

css-flexbox/Overview.bs

@@ -3,8 +3,7 @@
 <pre class='metadata'>
 Shortname: css-flexbox
 Level: 1
-Status: CR
-Date: 2016-03-01
+Status: ED
 Deadline: 2016-09-01
 Work Status: Testing
 Group: csswg
@@ -3367,6 +3366,120 @@ Changes since the 1 March 2016 CR</h3>
 
 	A <a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301">Disposition of Comments</a> is also available.
 
+<h4 id="change-201603-substantive">
+Substantive Changes and Bugfixes</h4>
+
+	<ul>
+		<li id="change-2016-intrinsic-percentage">
+			Define how percentages are handled when calculating intrinsic <a>automatic minimum sizes</a>.
+			(<a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301#issue-3">Issue 3</a>)
+			<blockquote>
+				<ins><p>
+					For the purpose of calculating an intrinsic size of the element
+					(e.g. the element's <a>min-content size</a>),
+					this value causes the element's size in that axis to become indefinite
+					(even if e.g. its 'width' property specifies a <a>definite</a> size).
+					Note this means that percentages calculated against this size
+					will be treated as ''height/auto''.
+				</p></ins>
+
+				<p>
+					<ins>Nonetheless,</ins>
+					although this may require an additional layout pass to re-resolve percentages in some cases,
+					this value
+					(like the ''min-content'', ''max-content'', and ''fit-content'' values defined in [[CSS3-SIZING]])
+					does not prevent the resolution of percentage sizes within the item.
+				</p>
+			</blockquote>
+		<li id="change-2016-definite-indefinite">
+			Switched <a>definite</a> and <a>indefinite</a> to refer to the (more correct) definitions in [[!CSS3-SIZING]]
+			instead of defining them inline in this module.
+			(<a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301#issue-10">Issue 10</a>)
+	</ul>
+
+<h4 id="change-201604-clarify">
+Clarifications</h4>
+
+	<ul>
+		<li id="change-2016-spatial-nav">
+			Clarify that spatial navigation modes are allowed to handle 'order'.
+			(<a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301#issue-1">Issue 1</a>)
+			<blockquote>
+				<ins><p class="note">
+					User agents, including browsers, accessible technology, and extensions,
+					may offer spatial navigation features.
+					This section does not preclude respecting the 'order' property
+					when determining element ordering in such spatial navigation modes;
+					indeed it would need to be considered for such a feature to work.
+					However a UA that uses 'order' in determining sequential navigation,
+					but does not otherwise account for spatial relationships among elements
+					(as expressed by the various layout features of CSS including and not limited to flex layout),
+					is non-conforming.
+			 </p></ins>
+			</blockquote>
+		<li id="change-2016-definite-3">
+			Cross-reference an additional case of definiteness in <a href="#definite-sizes"></a>
+			(<a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301#issue-2">Issue 2</a>)
+			<blockquote>
+				<ins><p>
+					Once the cross size of a flex line has been determined,
+					items in auto-sized flex containers are also considered
+					definite for the purpose of layout; see <a href="#algo-stretch">step 11</a>.
+				</p></ins>
+			</blockquote>
+		<li id="change-2016-auto-content-wording">
+			Improve wording for how unresolveable percentage <a>flex basis</a> values
+			transmute to ''content''.
+			(<a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301#issue-6">Issue 6</a>)
+			<blockquote>
+				<p>
+					For all values other than ''flex-basis/auto'' and ''content'' (defined above),
+					'flex-basis' is resolved the same way as 'width' in horizontal writing modes [[!CSS21]],
+					<ins>except that if a value would resolve to ''width/auto'' for 'width',
+					it instead resolves to ''content'' for 'flex-basis'</ins>.
+					For example, percentage values of 'flex-basis' are resolved against
+					the flex item's containing block (i.e. its <a>flex container</a>);
+					and if that containing block's size is <a>indefinite</a>,
+					<del>the result is the same as a <a>main size</a> of <a value for=width>auto</a>
+					(which in this case is treated as ''content'')</del>
+					<ins>the used value for 'flex-basis' is ''content''</ins>.
+				</p>
+			</blockquote>
+		<li id="change-2016-inflexible-definite">
+			Clarify that inflexible items with a <a>definite</a> <a>flex basis</a> have a <a>definite size</a>.
+			(<a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301#issue-8">Issue 8</a>,
+			 <a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301#issue-11">Issue 11</a>)
+			<blockquote>
+				<ins>
+					<p>A <a>flex item</a> is <a>fully inflexible</a>
+					if both its 'flex-grow' and 'flex-shrink' values are zero,
+					and <dfn>flexible</dfn> otherwise.</p>
+				</ins>
+			</blockquote>
+			<blockquote>
+				<ins><p class="note">
+					The main size of a <a>fully inflexible</a> item with a <a>definite</a> <a>flex basis</a>
+					is, by definition, <a>definite</a>.
+				</p></ins>
+			</blockquote>
+		<li id="change-2016-reword-min-auto">
+			Reworded definition of the ''min-width/auto'' value to be easier to understand.
+			(<a href="https://drafts.csswg.org/css-flexbox/issues-cr-20160301#issue-9">Issue 9</a>)
+			<blockquote>
+				<p>
+					On a <a>flex item</a> whose 'overflow' is ''overflow/visible'' in the <a>main axis</a>,
+					when specified on the <a>flex item's</a> main-axis min-size property,
+					<del>the following table gives the minimum size &hellip;</del>
+					<ins>specifies an <dfn dfn export>automatic minimum size</dfn>.</ins>
+				</p>
+				<ins><p>
+					In general, the <a>automatic minimum size</a> &hellip; defined below:
+				</p></ins>
+			</blockquote>
+		<li>Miscellaneous trivial editorial improvements.
+	</ul>
+
+
 <h3 id="changes-201505">
 Changes since the 14 May 2015 LCWD</h3>