Re: [csswg-drafts] [css-overflow-5] Bikeshed pseudoclasses for active scroll-marker (#10918)

> Iā€™d expect :target-shown to match every control whose scrollTargetElement is visible in the scroll port, and not just one. Maybe because it sounds a bit like :target-visible?

Right, I think it's a good thing to avoid visible. Whichever name we go with we would of course have clear text explaining the meaning.

The relation to [:target](https://drafts.csswg.org/selectors/#the-target-pseudo) is nice, though the behavior is not identical - as this will change with scrolling whereas `:target` would only change if the URL was updated. Some other options:
1. `:scroll-target`: perhaps a bit odd to have this match on the marker pointing to the target, rather than the target itself.
2. `:selected`: easily confused with text selection which uses `::selection`, also could be confused with `<select>` which uses `:checked` which is what we're trying to move away from.
4. `:current-target`: answers the "current what?" question from @kbabbitt and might be sufficiently distinct from both `:current` and `:target`
5. `:target-current`: while it doesn't conflict with the usage of `:current`, it could still be conflated for being related to `:current`.
6. `:target-nearest` (or some variation on "nearest"): feels a bit awkward but does match pretty closely to what is meant
7. `:target-active`: Doesn't actually mean that the target is `:active`, but maybe?

> it has the potential to set the path forward for many upcoming specs, too.

No pressure šŸ˜ 

This also suggests we should think about what terminology might make sense for similar non-form non-focus related active / selected states, e.g. the current tab

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


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

Received on Monday, 30 September 2024 17:25:42 UTC