[css-flexbox-1] Update Changes list.

Author: fantasai

css-flexbox-1/Overview.bs

@@ -3608,6 +3608,10 @@ Boris Zbarsky.
 <h3 id="changes-20181119">
 Changes since the <a href="https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/">19 November 2018 CR</a></h3>
 
+	A <a href="https://drafts.csswg.org/css-flexbox-1/issues-cr-2018">Disposition of Comments</a>
+	is available.
+	Significant changes include:
+
 	<ul>
 		<li id="change-2018-correctly-ignore-auto">
 			Correctly ignore ''width/auto'' [=preferred sizes=]
@@ -3619,20 +3623,64 @@ Changes since the <a href="https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/
 
 		<li id="change-2018-move-order">
 			Moved the 'order' property definition to [[CSS-DISPLAY-3]].
-			See [[#order-property]].
+			See [[#order-property]] for remaining explanation.
 			(<a href="https://github.com/w3c/csswg-drafts/issues/5865">Issue 5865</a>)
 
+		<li id="change-2018-definite-basis-definite">
+			Made [=main size=] always [=definite=] for [=flex items=] with a [=definite=] [=flex basis=],
+			to match implementations.
+			(<a href="https://github.com/w3c/csswg-drafts/issues/4311">Issue 4311</a>)
+			<blockquote>
+				<ol>
+					<li>If the [=flex container=] has a [=definite=] [=main size=],
+					<ins>then the post-flexing [=main sizes=]
+					of its [=flex items=]
+					are treated as [=definite=]</ins>
+					<del>a <a>flex item</a>’s post-flexing <a>main size</a>
+					is treated as <a>definite</a>,
+					even though it can rely on the <a>indefinite</a> sizes
+					of any flex items in the same line</del>.
+
+					<li><ins>If a [=flex-item’s=] [=flex basis=] is [=definite=],
+					then its post-flexing [=main size=] is also [=definite=].</ins>
+				</ol>
+			</blockquote>
+			<blockquote>
+				<p class="note"><del>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>.</del>
+
+				<p class="note"><ins>Note: This means that within [=flex layout=],
+				“definite” sizes can require performing layout.
+				This was done to allow percentages inside of [=flex items=]
+				to resolve where authors expected them to resolve.</ins>
+			</blockquote>
+
 		<li id="change-2018-bracket-range-notation">
 			Changed syntax to use <a>CSS bracketed range notation</a> to reflect the prose restrictions on negative values.
+			(Editorial.)
 
 		<li id="change-2018-preferred-aspect-ratio">
-			Update aspect ratio terminology to use the term [=preferred aspect ratio=],
-			and clarify any uses that are specific to [=replaced elements=].
+			Updated aspect ratio terminology to use the term [=preferred aspect ratio=],
+			and clarify any uses that are specific to [=replaced elements=],
+			in order to accommodate forthcoming 'aspect-ratio' property.
 
 		<li id="change-2018-collapsed-intrinsic-container">
 			Explicitly excluded [=collapsed flex items=]
 			from the [[#intrinsic-main-sizes|intrinsic main size calculations]].
 			(<a href="https://github.com/w3c/csswg-drafts/issues/5985">Issue 5985</a>)
+			<blockquote>
+				<p>The <strong><a>max-content</a> <a>main size</a> of a <a>flex container</a></strong>
+				is the smallest size the <a>flex container</a> can take
+				while maintaining the [[#intrinsic-item-contributions|max-content contributions]] of its <a>flex items</a>,
+				insofar as allowed by the items’ own flexibility.
+				<ins>Considering only non-[=collapsed=] [=flex items=]:</ins>
+			</blockquote>
+			<blockquote>
+				However, for a <em><a>multi-line</a></em> container,
+				it is simply the largest [[#intrinsic-item-contributions|min-content contribution]]
+				of all the <ins>non-[=collapsed=]</ins> <a>flex items</a> in the <a>flex container</a>.
+			</blockquote>
 
 		<li id="change-2018-used-cross-size">
 			Clarified that the [=flex base size=] calculations
@@ -3646,7 +3694,8 @@ Changes since the <a href="https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/
 
 		<li id="change-2018-flexible-length-text">
 			Slightly restructured the prose in [[#resolve-flexible-lengths]]
-			to resolve <a href="https://github.com/w3c/csswg-drafts/issues/5179">Issue 5179</a>.
+			to fix errors.
+			(<a href="https://github.com/w3c/csswg-drafts/issues/5179">Issue 5179</a>)
 
 		<li id="change-2018-cross-layout">
 			Clarified that “performing layout” means using the block-level layout rules.
@@ -3703,6 +3752,10 @@ Changes since the <a href="https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/
 			is a type of [=intrinsic size contribution=],
 			and thus impacted by associated rules in [[CSS-SIZING-3]].
 			(<a href="https://github.com/w3c/csswg-drafts/issues/5665#issuecomment-738391191">Issue 5665</a>)
+			<blockquote>
+				Note: The [=content-based minimum size=] is a type of [=intrinsic size contribution=],
+				and thus the provisions in [[css-sizing-3#intrinsic-contribution]] apply.
+			</blockquote>
 
 		<li id="change-2018-content-based-editorial">
 			Redrafted the definition of [=content-based minimum size=]
@@ -3712,6 +3765,13 @@ Changes since the <a href="https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/
 			Added [[#webkit-aliases]] to document <code>-webkit-</code> aliases of flex layout properties
 			that are necessary for Web-compat.
 			(<a href="https://github.com/w3c/csswg-drafts/issues/5634">Issue 5634</a>)
+
+		<li id="change-2018-blockification">
+			Rephrased blockification rules in terms of [=computed values=].
+			(<a href="https://github.com/w3c/csswg-drafts/issues/4065">Issue 4065</a>)
+
+		<li>
+			Various minor editorial fixes and clarifications,
 	</ul>
 
 <h3 id="changes-20171016">