- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Jun 2021 18:25:23 +0000
- To: public-css-archive@w3.org
Spec for WM4: https://www.w3.org/TR/css-writing-modes-4/#orthogonal-layout
Implementations, as Tab mentioned, cap the orthogonal flex/grid container itself rather than passing infinity through and letting descendant block containers cap.
The original thought behind passing infinite available space through vs using the viewport as a cap:
* For lines of text, laying out as max-content is problematic because it's hard to read such text. It's much, much more useful to wrap it to the viewport size.
* For flex and grid, laying out at max-content isn't as much of a problem because you're not reading line by line and having to scroll up and down for each line in the same way. (But the flex *items* should cap at the viewport size if they contain text, for the reason above.)
So there are two interesting questions here:
* Which do we think is the better behavior for CSS: capping the orthogonal item itself, or capping only block containers?
* If we think it's better to not cap orthogonal flex and grid containers themselves (but rather the block containers within them), is it worth asking implementations to change?
--
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4221#issuecomment-858872839 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 June 2021 18:26:45 UTC