- From: Adam Argyle via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 May 2023 18:06:05 +0000
- To: public-css-archive@w3.org
> developer naively sets `scroll-start-target: auto` on some element it won't scroll into view in the inline axis, right? This seems surprising `scroll-start-target-inline: auto` would, but I do like the suggestion 👍🏻 seems more surprising to have it not work in that shorthand case, then to have it work. > scroll to the intersection of all `scroll-start-target`s I hadnt considered a spec entry for intersection, like asking the browser to try and find the best scroll position given a target for each axis? i'm leaning towards a preference of being declarative about a scroll axis and requiring authors to specify which item they want scroll to start at. but i do clearly see how they can compete, where one item as the scroll target naturally puts the other out of view. Let me build some demo's, it may help us shake out the right behavior. > handling multiple targets i'll make a demo or two about this also, so we have something tangible to talk about. -- GitHub Notification of comment by argyleink Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8832#issuecomment-1548321339 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 May 2023 18:06:07 UTC