- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Apr 2023 22:01:59 +0000
- To: public-css-archive@w3.org
> It's the children who opt out of the default behavior by becoming scroll containers, so it's up to them to mitigate the negative effects. This is not really applicable to some of the real-world use-cases, where different teams can work on different components, and a design system needs to provide a component that is resilient and can accommodate whatever is thrown into it — in this case the component would _need_ to be split in two elements. So, the limitation of CSS leads to a bloated HTML. > I don't get it, why can you set overflow: hidden on a child but you can't set overflow: clip on a child? See above — a component would not know what exactly would be placed into it, and the child won't know in which container it would be placed. We could argue, that in that case the component shouldn't have the `display: flex` on it, but then that would mean that in case we'd want to add a flex layout inside, we'd _have_ to still use an extra wrapper to separate the overflow from flex. > Try Firefox. It seems Chrome has a bug Oh, interesting! Safari has the same bug, so I would need to look into if it exists in their bug trackers. > That's by design, you want safe center instead of center. https://drafts.csswg.org/css-align-3/#overflow-values TIL, though, a bit sad that it works only in Firefox for now. And, maybe you know — is it intended not to work with `space-around` or `space-around` values, or is it a Firefox bug? -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8725#issuecomment-1509986838 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 April 2023 22:02:01 UTC