W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2016

[csswg-drafts] [css-flexbox] Example 3 (on abspos flex items) mistakenly says `align-content` when it means `align-self`

From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
Date: Fri, 02 Sep 2016 06:13:37 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-174687983-1472796814-sysbot+gh@w3.org>
dholbert has just created a new issue for 

== [css-flexbox] Example 3 (on abspos flex items) mistakenly says 
`align-content` when it means `align-self` ==
Filing a bug on a typo in flexbox spec section [4.1. 
Absolutely-Positioned Flex 
Children](https://drafts.csswg.org/css-flexbox-1/#abspos-items) -- 
specifically, Example 3 inside that section.

Example 3 says:
> The effect of this is that if you set, for example, `align-content: 
center;` on an absolutely-positioned child of a flex container, auto 
offsets on the child will center it in the flex container’s cross 

I'm 95% sure that means to say `align-self`, NOT `align-content`, for 
several reasons:
 * This spec-text talking about applying this style *on the child*, 
with the intention of centering the child.  That's precisely what the 
`*-self` properties do -- position the thing they're applied to -- 
whereas the `*-content` properties control alignment *inside* of the 
thing they're applied to.
 * If the flex container is single-line, [another piece of the 
spec](https://drafts.csswg.org/css-flexbox-1/#flex-lines) *explicitly 
says* that "`align-content` has no effect" (because it's about 
aligning flex lines, and in a single-line flexbox, "the cross size of 
the line is the cross size of the flex container".

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/436 using your GitHub 
Received on Friday, 2 September 2016 06:13:44 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:02 UTC