Snapchanged events allow developers reliably listen for when the "snap target" of a scroller changes and perform style adjustments as necessary/desired. CSS scroll snap points are often used as a mechanism to create scroll interactive "selection" components, where selection is determined with javascript intersection observers and a scroll end guestimate. By creating a built-in event, the invisible state will become actionable, at the right time, and always correct.
This event will help developers synchronize a snapped scroll item with the rest of their interface elements efficiently and effectively.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
No milestones specified