- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Sep 2020 21:40:37 +0000
- To: public-css-archive@w3.org
> Proposals here should also keep in mind the proposed `scrollend` event: https://github.com/WICG/overscroll-scrollend-events Thank you for the note, @smfr! The information related to snapping for the proposed `snapped` event _might_ be mingled into the `scrollend` event, as both happen after the scrolling action has finished. Though I believe both events are distinct enough to be handled separately. This is especially true if we consider adding several events related to snapping. The order in which they'd get fired is probably not that important as both are defined not to be cancelable and `scrollend` is currently defined as being async, but logically snapping causes the scroll action to end, so I'd say `snapped` before `scrollend`. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/156#issuecomment-695839922 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 20 September 2020 21:40:39 UTC