- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Sat, 18 Jun 2022 23:12:07 +0000
- To: public-css-archive@w3.org
> Feels kinda odd that if a 100px-wide scroller has a single 90px-wide child, it'll act like `hidden`, but if it the child is 110px wide, it'll loop itself. Maybe I'm overthinking it? I just took that from the `auto` value. What I actually wanted to say with that is that the content will just get displayed as is in that case. It won't get fragmented or duplicated or anything fancy. Though, re-thinking this, users probably expect the behavior to be the same in both cases. I.e. we might say that the empty space will be fragmented like an element in that case. So, picking up your example of a 100px-wide scroller with a 90px-wide child, you'd still be able to scroll. That means, the child and the 10px empty space would be fragmented so that they always fill up the 100px width of the scroller. So, showing my perfect drawing skills again 😉 using the example from above, that would then look like this when being scrolled:  Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5411#issuecomment-1159579919 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 18 June 2022 23:12:08 UTC