Re: [csswg-drafts] [css-overflow-5] Creating scroll-marker groups within which to select an active marker (#10916)

The main thing is that one of the markers within the `scroll-marker-contain: auto` group would match `:target-current`.

> Ideally we'd also get [the `focusgroup` behavior](https://open-ui.org/components/focusgroup.explainer/), where the entire group is a single tabstop, the arrow keys move focus within the group).

We could apply focus-group behavior or we could leave focusgroup as an independent thing you might want to set. On its own, applying focusgroup only makes it so that when one is focused you can move to the other links by using the arrow keys (see the links on the left-hand side of https://flackr.github.io/carousel/examples/scroll-marker/scrolltarget/ ).

> and the group remembers its last selected option when you tab out of it so it can reselect the same one when you tab back to it (or, if you've scrolled since then, it selects the one currently matching how the page is scrolled

This particular behavior is only if you also set tabindex=0 (see the links on the right-hand side of https://flackr.github.io/carousel/examples/scroll-marker/scrolltarget/ ). If there are focusable elements within the focusgroup you can't tell that there is a last focused element

There is also a question of if this changes the activation behavior. Normally activating a link `<a href="#target">` will perform a "navigation" updating the URL, and scroll every scroller to the root into view. I think that the simplest would be to keep the full activation behavior (when clicked or focused and activated, not when focusing it via arrow keys in the focus group which would only scroll).

-- 
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10916#issuecomment-2487021260 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 20 November 2024 00:10:50 UTC