web-platform-tests / web-platform-tests/interop

Scroll markers

Open
#1,406 1 comment 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

focus-area-proposal
Dominant language
JavaScript
Stars
524
Forks
35
Avg merge
1d 4h
Merged PRs (30d)
10

Description

Description

Prior requests : #1131

Description

Scroll containers have evolved beyond carousel pagination and other scrollable interfaces and are now capable of providing interfaces for tabs and wizards as demonstrated at Chrome Carousel Gallery .The ::scroll-marker and ::scroll-marker-group pseudo-elements provide native, styleable navigation for scroll containers.

Today, developers treat these patterns as separate components, often implementing and managing each one with JavaScript. Making scroll markers interoperable would allow them to share a common browser-managed primitive. It would also reduce the accessibility problems caused by repeatedly reimplementing the same interaction patterns.

Specification

https://drafts.csswg.org/css-overflow-5/#scroll-markers

web-feature

https://web-platform-dx.github.io/web-features-explorer/features/scroll-markers/

Test Links

https://wpt.fyi/results/css/css-overflow?label=master&label=experimental&aligned&q=scroll-marker

Additional Signals

Standards Positions:

Mozilla: https://github.com/mozilla/standards-positions/issues/1161
WebKit: https://github.com/WebKit/standards-positions/issues/447

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing scroll-marker results under css/css-overflow on the linked WPT dashboard and compare them with the CSS Overflow 5 scroll-markers specification. Add the missing interoperability coverage for ::scroll-marker and ::scroll-marker-group, then verify the relevant tests report consistently across implementations.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.