W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2017

[csswg-drafts] [css-align] definitions of baseline content-alignment seem wrong about which side it adds padding to

From: L. David Baron via GitHub <sysbot+gh@w3.org>
Date: Sat, 20 May 2017 01:26:05 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-230121405-1495243564-sysbot+gh@w3.org>
dbaron has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-align] definitions of baseline content-alignment seem wrong about which side it adds padding to ==
The rules on how to add extra space for baseline content-alignment seem to be duplicated (in slightly different form) between [Baseline Content-Alignment](https://drafts.csswg.org/css-align/#baseline-align-content) and [Aligning Boxes by Baseline](https://drafts.csswg.org/css-align/#align-by-baseline).  However, the former says that padding when aligning to first (last) baseline is added on the start (end) side, and the latter seems to say roughly the same except without specifying that it's padding that's added.

This seems to assume that the `align-self` of a first (last) baseline aligned element is always start (end).  However, I don't see anything that ensures this, and in fact I could imagine it being a useful feature to not ensure this.  However, it might also be rather difficult to implement, and I think it needs to be thought through a bit.

For example, in a horizontal flex container, suppose you apply `align-content: baseline` to two `display:block` flex items, one of which has `align-self: end` one has `align-self: start`.  Any padding added for first baseline alignment will certainly be added to the bottom of the first, and the top of the second.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1411 using your GitHub account
Received on Saturday, 20 May 2017 01:26:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 10:12:53 UTC