Created attachment 295409 [details] Test case to reproduce the issue. According the the last draft version of the Flexible Box specification: https://drafts.csswg.org/css-flexbox/#flex-baselines "if the flex container has at least one flex item, the flex container’s first/last main-axis baseline set is generated from the alignment baseline of the first/last flex item. (If that item has no alignment baseline parallel to the flex container’s main axis, then one is first synthesized from its border edges.)" The CSS WG has agreed as well that we should do the same for orthogonal flex items: https://github.com/w3c/csswg-drafts/issues/373 https://lists.w3.org/Archives/Public/www-style/2016Sep/0000.html Also, while I couldn't find it in the specs, the CSS WG has agreed that an empty Flexbox containers should synthesize its baseline using its border-box bottom edge: https://github.com/w3c/csswg-drafts/issues/439 The attached test cases prove that current implementation doesn't follow the spec.
<rdar://problem/29694866>
> "if the flex container has at least one flex item, the flex container’s first/last main-axis baseline set is generated from the alignment baseline of the first/last flex item. (If that item has no alignment baseline parallel to the flex container’s main axis, then one is first synthesized from its border edges.)" We seem to do this now. > Also, while I couldn't find it in the specs, the CSS WG has agreed that an empty Flexbox containers should synthesize its baseline using its border-box bottom edge: It appears WebKit, Blink, and Gecko all use the margin-box for empty flexbox containers currently; not totally sure what css-flexbox and css-align say now? So is this now resolved?
Created attachment 466272 [details] Safari / WebKit matches with other browsers As per attached, WebKit / Safari is matching other browsers. Do we need to do anything here?
Closing based on Ahmad's testing.