web-platform-tests / web-platform-tests/interop
Scroll snap events
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 524
- Forks
- 35
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Description
The CSS Scroll Snap events, “scrollsnapchange” and “scrollsnapchanging”, give developers precise control over advanced interfaces through quick and easy access to information about scroll snap interactions on the page.
Developers can currently use a combination of IntersectionObserver and scroll events to create a loose approximation. But that is inefficient for both the developer experience and browser’s performance, with the information not guaranteed to be accurate.
Scroll Snap Events make the task trivial while being tied to the browser’s own scroll snap mechanisms. Which is more accurate and performant.
Chromium is currently the only browser engine to support Scroll Snap Events. The Chrome team published this blog post introducing the feature:
https://developer.chrome.com/blog/scroll-snap-events
Specification
https://www.w3.org/TR/css-scroll-snap-2/#snap-events
web-feature
https://web-platform-dx.github.io/web-features-explorer/features/scroll-snap-events/
Test Links
No response
Additional Signals
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CSS Scroll Snap 2 specification and the linked web-features explorer entry, then compare the stated Chromium support with other browser engines. Determine the interoperability scope for scrollsnapchange and scrollsnapchanging; done should mean that the scope and required test coverage are clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- testing-qa, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100