- From: shanthambi via GitHub <noreply@w3.org>
- Date: Wed, 17 Dec 2025 10:28:47 +0000
- To: public-css-archive@w3.org
@flackr In the same setup, scroll-marker scrolls to the expected snap-aligned position, but scroll-button consistently scrolls only ~85% of the required distance, leaving the target slide partially visible. Since both scroll-marker and scroll-button are part of the same CSS Carousel mechanism, they should resolve to the same scroll snap positions and produce identical final scroll offsets. The current behavior makes scroll-button unreliable, even though the snap points themselves are correct (as demonstrated by scroll-marker). From an authoring perspective, this inconsistency makes it impossible to rely on CSS carousel controls without JavaScript fallbacks, especially for predictable and accessible navigation. I can also reproduce this using the demo below. Tested in Chrome Version 143.0.7499.41. This highlights an inconsistency between scroll-marker and scroll-button, which should both resolve to the same scroll snap positions. https://codepen.io/shan071/pen/gbrNMXg -- GitHub Notification of comment by shanthambi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10914#issuecomment-3664696633 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 December 2025 10:28:48 UTC