- From: Sarah Higley via GitHub <noreply@w3.org>
- Date: Thu, 18 Sep 2025 17:34:06 +0000
- To: public-css-archive@w3.org
I think my initial confusion around it triggering focusability was caused by a personal issue with janky horizontal scroll behavior when I was testing, so I thought it just didn't support mouse/keyboard scroll 😅. Given it does, that seems OK. The central issue is still the authoring need to be able to call focus on the container separately from the scroll markers, together with the following: - When focus is on the scroll markers, it should be possible to find the current and next/previousfocusable element through using `document.activeElement` - When looking for the next/previous focusable element starting from either something within the carousel or after it, it should be possible to query & find the scroll markers separately from the container (also based on where they are in the DOM in relation to other focusable elements, which is different from where the container is) From the perspective of a library maintainer, those should ideally be possible for every possible way to author a carousel, since the team writing focus management code is often not the team writing the carousel code. -- GitHub Notification of comment by smhigley Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12240#issuecomment-3308726442 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 September 2025 17:34:07 UTC