[css-flex] Flex container baseline wrongly uses content-box bottom to synthesize baselines |
|||
Issue descriptionAccording 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.
,
Oct 27 2016
,
Dec 5 2016
,
Jan 16 2017
cbiesinger@ what do you think about this issue ? It's pretty clear that this is a change in the Flexbox specs that makes wrong the current Flexbox implementation in Chrome. I'm worried about backward compatibility issues if we modify this behavior, but I'd need such change to complete the implementation for grid, which also uses the border-box to synthesize grid item's baseline when needed (empty or orthogonal items).
,
May 21 2018
Any update here Christian? |
|||
►
Sign in to add a comment |
|||
Comment 1 by cbiesin...@chromium.org
, Oct 26 2016