- From: Mason Freed via GitHub <noreply@w3.org>
- Date: Mon, 15 Sep 2025 17:49:53 +0000
- To: public-css-archive@w3.org
> This isn't related to `scroll-marker-group`, but rather just making it a scroll container, see https://chromestatus.com/feature/5231964663578624. I.e. just having a scroll container makes it focusable https://jsbin.com/yufibuw/edit?html,css,js,output > > [@mfreed7](https://github.com/mfreed7) you're listed an owner on this feature and maybe have more context about where this was discussed. Right - starting with Chrom(ium) 132, scroll containers are focusable, and they become keyboard focusable (part of the sequential focus navigation order) if they do not contain any other focusable descendants. > [@flackr](https://github.com/flackr) I'm curious if you think the `scroll-marker-group` behavior should also trigger focusability in the same way that regular scroll should. The reason for it happening with a traditional scroll overflow element is so keyboard users can scroll, but that doesn't really apply to scroll marker containers. Mouse scrolling doesn't do anything, and keyboard arrows don't scroll in the traditional way. This is an interesting point. Do you think we should modify the above heuristic in some way to avoid that treatment for scroll marker containers? That would (I think?) be relatively easy to do, if it's the correct thing to do. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12240#issuecomment-3293294924 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 September 2025 17:49:54 UTC