Skip to content

[css-overflow-5] Update scroll-marker-group to include modes #12122#13627

Merged
danielsakhapov merged 2 commits into
w3c:mainfrom
danielsakhapov:scroll-marker-group-modes
Mar 17, 2026
Merged

[css-overflow-5] Update scroll-marker-group to include modes #12122#13627
danielsakhapov merged 2 commits into
w3c:mainfrom
danielsakhapov:scroll-marker-group-modes

Conversation

@danielsakhapov

Copy link
Copy Markdown
Contributor

No description provided.

@danielsakhapov danielsakhapov requested a review from flackr March 11, 2026 10:17
Comment thread css-overflow-5/Overview.bs Outdated

* The roles of ''::scroll-marker-group'' and ''::scroll-marker'' are `navigation` and `link` respectively.
* All ''::scroll-marker'' pseudo-elements are tab stops, in order.
* Activating a ''::scroll-marker'' pseudo-element <a lt='scroll a target into view'>scrolls its originating element into view</a> and sets the <a href="https://html.spec.whatwg.org/multipage/interaction.html#sequential-focus-navigation-starting-point">sequential focus navigation starting point</a> to the [=originating element=], losing focus from the ''::scroll-marker''.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The activation behavior is also specified in the activation section. I think in practice we try to have a single normative specification and if there are additional locations they are non-normative (e.g. notes).

TLDR; can we either:

  • remove the activation behavior here and add references to the sections explaining the behavioral changes based on the mode from this section, or
  • in the activation behavior section, instead of having a switch, call to this section to invoke mode specific activation behavior

@danielsakhapov danielsakhapov requested a review from flackr March 11, 2026 15:22
@danielsakhapov danielsakhapov merged commit c8a7880 into w3c:main Mar 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants