- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Sep 2022 03:41:48 +0000
- To: public-css-archive@w3.org
bfgeek has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-flexbox-1] Flex container baselines with reverse direction. == Consider: https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=10775 ```html <!DOCTYPE html> baseline <div style="border: solid 3px; display: inline-flex; flex-direction: row-reverse;"> <div style="background: lime;">a</div> <div style="background: hotpink; font-size: 30px;">b</div> </div> ``` Here all implementions pick up the "a" baseline (logically last), instead of the "b". Similar for column flexboxes: https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=10776 Following this logic for "last baseline" would mean the last baseline is at the top. (Note Firefox doesn't appear to support this case - unsure what its doing). Are implementations correct? I believe implementations are incorrect per-spec - from: https://drafts.csswg.org/css-flexbox-1/#flex-baselines "To this end, the baselines of a flex container are determined as follows (after reordering with [order](https://drafts.csswg.org/css-display-3/#propdef-order), and taking [flex-direction](https://drafts.csswg.org/css-flexbox-1/#propdef-flex-direction) into account):" But should be explicit. Note there are several WPTs asserting this behaviour. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7776 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 September 2022 03:41:50 UTC