CSS scroll snap points are often used as a mechanism to create interactive scroll "selection" components, giving authors control over what areas of its content a scrolling container can settle. This proposal adds 2 JavaScript events, “snapchanging” and “snapchanged”, which fire in response to the scrolling/snapping of containers which snap. snapchanging is a JavaScript event that aims to let the web page know, as early as possible, that a scrolling operation will result in a change in the element the container being scrolled is snapped to. snapchanged is a JavaScript event that fires when a scrolling operation is complete and the scroller has snapped to a different element than it was previously snapped to.
こんにちは TAG-さん!
I'm requesting a TAG review of Snap Events.
CSS scroll snap points are often used as a mechanism to create interactive scroll "selection" components, giving authors control over what areas of its content a scrolling container can settle. This proposal adds 2 JavaScript events, “snapchanging” and “snapchanged”, which fire in response to the scrolling/snapping of containers which snap. snapchanging is a JavaScript event that aims to let the web page know, as early as possible, that a scrolling operation will result in a change in the element the container being scrolled is snapped to. snapchanged is a JavaScript event that fires when a scrolling operation is complete and the scroller has snapped to a different element than it was previously snapped to.
Explainer¹ (minimally containing user needs and example code): Snapchanged: https://github.com/argyleink/ScrollSnapExplainers/tree/main/js-snapChanged Snapchanging: https://github.com/argyleink/ScrollSnapExplainers/tree/main/js-snapChanging
Specification URL: https://drafts.csswg.org/css-scroll-snap-2/#snap-events
Tests: [wpt folder(s), if available] https://wpt.fyi/results/css/css-scroll-snap-2/snapchanging https://wpt.fyi/results/css/css-scroll-snap-2/snapchanged
User research: [url to public summary/results of research] N/A
Security and Privacy self-review²: As indicated in the explainer, there are no known privacy or security issues.
GitHub repo (if you prefer feedback filed there):
Primary contacts (and their relationship to the specification):
Organization(s)/project(s) driving the specification: CSSWG
Key pieces of existing multi-stakeholder (e.g. developers, implementers, civil society) support, review or discussion of this specification:
External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):
Further details: