- From: Nikolas Schröter via GitHub <noreply@w3.org>
- Date: Thu, 27 Aug 2026 16:49:03 +0000
- To: public-css-archive@w3.org
nwidynski has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-overflow-5] Add `currenttargetchange` event to scroll containers participating in a `scroll-marker-group` == A [scroll-marker-group](https://drafts.csswg.org/css-overflow-5/#propdef-scroll-marker-group) can operate in either **links** or **tabs** mode based on the [scroll-marker-group](https://drafts.csswg.org/css-overflow-5/#propdef-scroll-marker-group) property value. Today, this is not the case for a [scroll-target-group](https://drafts.csswg.org/css-overflow-5/#scroll-target-group) in **auto** mode, which only supports anchor tags. It would be nice if developers had further markup options to customize accessibility and localization in scenarios where rendering anchor tags isn't the appropriate accessibility choice. An example of one such use-case would be a **tabs pattern** based carousel built on `scroll-target-group` due to localization needs. Since markup may take many shapes I propose this to be solved with a new event, `currenttargetchange`, fired on the nearest common ancestor [scroll container](https://drafts.csswg.org/css-overflow-3/#scroll-container) of all of the [scroll marker](https://drafts.csswg.org/css-overflow-5/#scroll-marker) elements in the group. It would dispatch whenever the browser [calculates the active marker](https://drafts.csswg.org/css-overflow-5/#active-scroll-markers-calculation) and would neither bubble, nor compose. It would however fire regardless of whether or not a marker has been rendered in the target group, since the event itself may drive rendering of a marker of any type. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/14403 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 August 2026 16:49:04 UTC