Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Chrome 129 supports scroll snap events —
scrollsnapchange
andscrollsnapchanging
, which enable code being fired in response to a new scroll snap target being snapped to, and the browser identifying a change in the next snap target to be snapped to (if the gesture were to end).See the associated ChromeStatus entry and the Scroll Snap Events blog post for more context and a guide.
This PR adds the new events, and the
SnapEvent
event object.Note: The spec defines the associated event handler properties as being defined on the
GlobalEventHandlers
mixin, but I've added the events to theElement
object, as we no longer documentGlobalEventHandlers
. Let me know if you think it should sit somewhere else.Test results and supporting details
Related issues