- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Aug 2018 20:02:19 +0000
- To: public-css-archive@w3.org
dholbert has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-align] "Baseline Content-Alignment" spec text seems to incorrectly assume that align-content axis is always block axis == Spec link: https://drafts.csswg.org/css-align/#baseline-align-content This text has multiple references to the item's "inline axis" -- e.g. > Flex Items: > A flex item participates in first (last) baseline content-alignment in its flex line if its computed align-content is first baseline (last baseline) and **its inline axis** is parallel to the main axis. > Grid Items: > A grid item participates in first (last) baseline content-alignment in its startmost (endmost) row or column (whichever is parallel to **its inline axis**) and if its computed align-content is first baseline (last baseline). To me, this reliance on the item's "inline axis" indicates that there's an assumption that "align-content" will always be having an impact that is orthogonal to the item's inline axis (i.e. shifting its contents up or down, in a horizontal-tb writing mode). However: if the item happens to **be a flex container with `flex-direction:column`**, then align-content operates in the opposite axis from what it would normally operate in. (i.e. it would shift contents right or left, in a horizontal-tb writing mode) So it seems odd that there's a dependency on the element's inline axis in particular -- I think perhaps this spec text really means to say "inline axis [or main axis, if the item is a flex container]"? Caveat: I haven't implemented this `align-content:baseline` behavior yet, for flexbox -- I'm just trying to wrap my mind around how it should work. CC @tabatkins @fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3005 using your GitHub account
Received on Thursday, 9 August 2018 20:02:22 UTC