- From: Adam Argyle via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Apr 2023 15:30:16 +0000
- To: public-css-archive@w3.org
cool use case, totally makes sense. to me though, sounds like container queries are the perfect way to handle this: ```css .snap-scroll-inline { overflow-inline: scroll; scroll-snap-type: inline mandatory; container-type: inline-size; container-name: carousel; } @container carousel (width >= 720px) { .snap-scroll-inline > :nth-child(-n+2) { scroll-start-target-inline: auto; } } ``` So mobile does no scroll start adjusting, aligns inline-start nicely with the rest of a column layout design. but if width goes above 720, then set the scroll start target as to "peek" and "hint" at the carousel breadth of content by setting the scroll start target to something other than the first item. thoughts on using container queries to manage a carousels available space and dynamic scroll start positioning? -- GitHub Notification of comment by argyleink Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6986#issuecomment-1511600979 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 17 April 2023 15:30:18 UTC