@@ -3444,7 +3444,7 @@ Changes since the 26 May 2016 CR</h3>
34443444Substantive Changes and Bugfixes</h4>
34453445
34463446 <ul>
3447- <li id="change-2017 -box-sizing-basis">
3447+ <li id="change-2016 -box-sizing-basis">
34483448 To allow flex factors to actually represent absolute ratios of flex item sizes
34493449 as was originally intended (see various examples),
34503450 removed the flooring of content-box sizes at zero
@@ -3482,7 +3482,7 @@ Substantive Changes and Bugfixes</h4>
34823482 it's a max violation.
34833483 If the item's <a>target main size</a> was made larger by this,
34843484 </blockquote>
3485- <li id="change-2017 -max-contribution">
3485+ <li id="change-2016 -max-contribution">
34863486 To prevent empty flex items in shrink-to-fit containers
34873487 from collapsing to zero even when given a specified size,
34883488 the specified size is now accounted for in calculating
@@ -3496,7 +3496,7 @@ Substantive Changes and Bugfixes</h4>
34963496 and/or as a minimum (if it is not shrinkable),
34973497 and then further clamped by its <a lt="min main size property">min</a> /<a>max main size properties</a> .
34983498 </blockquote>
3499- <li id="change-2017 -definite-basis">
3499+ <li id="change-2016 -definite-basis">
35003500 Since at least two implementations ended up
35013501 allowing percentages inside flex items with indefinite flex basis to resolve anyway,
35023502 removed the condition requiring definite flex basis.
@@ -3512,10 +3512,23 @@ Substantive Changes and Bugfixes</h4>
35123512 For ease of implementation, ''align-self/auto'' value of 'align-self' now computes to itself always.
35133513 See <a href="change-2015-align-self-auto">related previous change</a>
35143514 requiring this computation for absolutely-positioned elements.
3515- (<a href="https://github.com/w3c/csswg-drafts/issues/440">Issue 440</a> )
3515+ (<a href="https://github.com/w3c/csswg-drafts/issues/440">Issue 440</a> ,
3516+ <a href="https://github.com/w3c/csswg-drafts/issues/644">Issue 644</a> )
3517+ <blockquote>
3518+ <table class="data">
3519+ <tr><th> Computed value: <td><del> <a value for=align-self>auto</a> computes to parent's 'align-items' value; otherwise</del> as specified
3520+ </table>
3521+ …
3522+ <p><del> On absolutely positioned elements,
3523+ a value of ''align-self/auto' computes to itself.
3524+ On all other elements, a value of '' aligh-self/auto'' for 'align-self'
3525+ computes to the value of 'align-items' on the element’s parent,
3526+ or '' align-self/stretch'' if the element has no parent.</del>
3527+ </blockquote>
35163528 <li id="change-2016-baseline-alignment">
35173529 Change <a>flex items</a> in orthogonal flows and <a>flex items</a> without a baseline
35183530 to both synthesize their alignment baseline from the <a>flex item</a>’s border box.
3531+ (<a href="">Issue XXX</a>)
35193532 <li id="change-2016-main-cross-baseline">
35203533 Fix main/cross error in definition of <a>cross-axis baseline set</a>.
35213534 (<a href="https://github.com/w3c/csswg-drafts/issues/792">Issue 792</a>)
@@ -3551,6 +3564,7 @@ Substantive Changes and Bugfixes</h4>
35513564 <li>When clamping by the <a>max main size property</a>
35523565 in the <a href="#intrinsic-main-sizes">calculation of the flex container’s intrinsic size</a>,
35533566 be sure to floor by the <a>min main size property</a>.
3567+ (<a href="https://github.com/w3c/csswg-drafts/issues/361">Issue 361</a>)
35543568 <blockquote>
35553569 <p>Within each line,
35563570 find the largest <var>max-content flex fraction</var>
@@ -3562,15 +3576,100 @@ Substantive Changes and Bugfixes</h4>
35623576 then clamp that result by the <a>max main size property</a>
35633577 <ins>floored by the <a>min main size property</a></ins>.</p>
35643578 </blockquote>
3579+ <li id="change-2016-abspos-no-order-fix">
3580+ Added missing edits for <a href="#change-2016-abspos-no-order">change</a>
3581+ that made 'order' not apply to absolutely-positioned children of a flex container.
3582+ (<a href="https://github.com/w3c/csswg-drafts/issues/1439">Issue 1439</a>)
3583+ <blockquote>
3584+ <table class="data">
3585+ <tr><th>Applies to: <td><a>flex items</a> <del>and absolutely-positioned children of <a>flex containers</a></del>
3586+ </table>
3587+ <p>
3588+ The 'order' property controls the order in which
3589+ <del>children of a flex container</del> <ins>flex items</ins>
3590+ appear within the flex container,
3591+ by assigning them to ordinal groups.
3592+ …
3593+ </p>
3594+ <p>
3595+ <ins>Absolutely-positioned children of a <a>flex container</a>
3596+ are treated as having '' order: 0''
3597+ for the purpose of determining their painting order relative to <a>flex items</a>.</ins>
3598+ </p>
3599+ </blockquote>
3600+ <blockquote>
3601+ Unless otherwise specified by a future specification,
3602+ this property has no effect on boxes that are not
3603+ <del>children of a <a>flex container</a></del> <ins><a>flex items</a></ins>.
3604+ </blockquote>
3605+ <li id="change-2016-flex-direction-baseline">
3606+ Take 'flex-direction' into account when determining first/last baseline of the flex container.
3607+ (<a href="https://github.com/w3c/csswg-drafts/issues/995">Issue 995</a>)
3608+ <blockquote>
3609+ <p>
3610+ To this end,
3611+ the baselines of a flex container are determined as follows
3612+ (after reordering with 'order'<ins>,
3613+ and taking 'flex-direction' into account</ins>):
3614+ </p>
3615+ <p>…</p>
3616+ <ol>
3617+ <li>
3618+ If any of the <a>flex items</a> on the flex container's
3619+ <del>first/last</del> <ins>startmost/endmost</ins> <a>flex line</a>
3620+ <a href="#baseline-participation">participate in baseline alignment</a>,
3621+ the flex container's first/last <a>main-axis baseline set</a> …
3622+ <li>
3623+ Otherwise, if the flex container has at least one <a>flex item</a>,
3624+ the flex container's first/last <a>main-axis baseline set</a>
3625+ is <a lt="generate baselines">generated</a> from
3626+ the <a>alignment baseline</a> of the
3627+ <del>first/last</del> <ins>startmost/endmost</ins> <a>flex item</a>.
3628+ …
3629+ <li>
3630+ Otherwise, the flex container has no first/last main-axis <a>baseline set</a>, …
3631+ </ol>
3632+ <p>…</p>
3633+ <ol>
3634+ <li>
3635+ If the flex container has at least one <a>flex item</a>,
3636+ the flex container's first/last <a>cross-axis baseline set</a>
3637+ is <a lt="generate baselines">generated</a> from
3638+ the <a>alignment baseline</a> of the
3639+ <del>first/last</del> <ins>startmost/endmost</ins> <a>flex item</a>.
3640+ …
3641+ </ol>
3642+ </blockquote>
3643+ <li id="change-2016-space-between-single-line">
3644+ Define '' align-content: space-between'' handling of a single <a>flex line</a>
3645+ as equivalent to '' align-content/start''.
3646+ (<a href="https://github.com/w3c/csswg-drafts/issues/718">Issue 718</a>)
3647+ <blockquote>
3648+ <p>
3649+ Lines are evenly distributed in the flex container.
3650+ If the leftover free-space is negative
3651+ <ins>or there is only a single <a>flex line</a> in the flex container,</ins>
3652+ this value is identical to <a value for=align-content>flex-start</a>.
3653+ </blockquote>
3654+ <li id="change-2016-axis-error">
3655+ Fixed error in <a href="#axis-mapping">axis mapping table</a>.
3656+ (<a href="https://github.com/w3c/csswg-drafts/issues/205">Issue 205</a>)
3657+ <li id="change-2016-reword-min-auto-fix">
3658+ Restored definition of the <a>automatic minimum size</a>
3659+ of boxes with neither <a>specified size</a> nor <a>aspect ratio</a>,
3660+ which was lost in earlier <a href="#change-2016-reword-min-auto">rewrite</a>.
3661+ (<a href="https://github.com/w3c/csswg-drafts/issues/671">Issue 671</a>)
35653662 </ul>
35663663
35673664<h4 id="change-201605-clarify">
35683665Clarifications</h4>
35693666 <ul>
3570- <li> Made sure that <a>main size</a> and <a>cross size</a> are defined
3667+ <li id="change-2016-main-cross-def">
3668+ Made sure that <a>main size</a> and <a>cross size</a> are defined
35713669 for <a>flex containers</a> as well as for <a>flex items</a>.
35723670 (<a href="https://github.com/w3c/csswg-drafts/issues/981">Issue 981</a>)
3573- <li> Tweaked final clarifying sentence of note about spatial navigation.
3671+ <li id="change-2016-broken-spatial-note">
3672+ Tweaked final clarifying sentence of note about spatial navigation.
35743673 (<a href="https://github.com/w3c/csswg-drafts/issues/1677">Issue 1677</a>)
35753674 <blockquote>
35763675 <p class="note">
@@ -3588,6 +3687,7 @@ Clarifications</h4>
35883687 A well-implemented spatial navigation feature would need to consider
35893688 all the layout features of CSS that modify spatial relationships.</ins>
35903689 </blockquote>
3690+ <li>Miscellaneous trivial editorial improvements.
35913691 </ul>
35923692
35933693<h3 id="changes-20160301">
@@ -3633,7 +3733,7 @@ Substantive Changes and Bugfixes</h4>
36333733 (<a href="https://drafts.csswg.org/css-flexbox-1/issues-cr-20160301#issue-13">Issue 13</a>))
36343734 </ul>
36353735
3636- <h4 id="change-201604 -clarify">
3736+ <h4 id="change-201603 -clarify">
36373737Clarifications</h4>
36383738
36393739 <ul>
@@ -4319,7 +4419,8 @@ Clarifications</h4>
43194419 </blockquote>
43204420
43214421 <li id="change-201403-abspos-ordering">
4322- Clarified application of 'order' to absolutely-positioned children of the <a>flex container</a> :
4422+ Clarified application of 'order' to absolutely-positioned children of the <a>flex container</a>.
4423+ (Note, this behavior was later <a href="#change-2016-abspos-no-order">rescinded</a>.)
43234424
43244425 <blockquote>
43254426 <p>An absolutely-positioned child of a flex container does not participate in flex layout
0 commit comments