Scrollend Events

[jgraham]

Description

The scrollend event is fired when a scroll is completed. Not only is this helpful for web developers that wish to be notified when a scroll is completed, but this has the potential to improve the reliability of other wpt tests. (See the various wait for scroll end functions that currently exist).

Specification

https://drafts.csswg.org/cssom-view/ (scrollend, scroll-completed, and scrolling-events)

Open Issues

No response

Tests

dom/events/scrolling/scrollend-*

Current Implementations

• [X] Blink
• [X] Gecko
• [ ] WebKit

Standards Positions

https://github.com/WebKit/standards-positions/issues/150

Browser bug reports

https://bugs.webkit.org/show_bug.cgi?id=201556 https://bugzilla.mozilla.org/show_bug.cgi?id=1785102

Developer discussions

No response

Polls & Surveys

No response

Existing Usage

Chrome use counter.

Workarounds

No response

Accessibility Impact

No response

Privacy Impact

No response

Other

No response

[jgraham]

CC @dlrobertson @hiikezoe @theres-waldo

[dlrobertson]

Note that the scrollend tests currently make use of touch scrolls for many of the tests. While testing scrollend for touch scrolls is helpful. It might make sense to move the vast majority of the webdriver action driven scrolls to use a normal scroll. See https://github.com/web-platform-tests/wpt/issues/42324.

[gsnedders]

Given Safari doesn't support touch events on macOS, the tests as currently written would still fail even if Safari supported scrollend.

[dlrobertson]

Given Safari doesn't support touch events on macOS, the tests as currently written would still fail even if Safari supported scrollend.

@gsnedders yeah that makes sense. I'll create a PR to update the tests.

[foolip]

@dlrobertson did you get around to updating tests?

@gsnedders could this be tested with a scroll wheel fling? It is possible to scroll on macOS, as a user, after all :)

[dlrobertson]

@dlrobertson did you get around to updating tests?

I just created https://github.com/web-platform-tests/wpt/pull/43493. Note that the following tests were not updated:

• ./dom/events/scrolling/scrollend-event-fired-to-element-with-overscroll-behavior.html - This test contains a test that ensures a scrollend is fired after a overscroll animation is run. I'm not sure how to test this without a touch scroll with the current webdriver APIs.
• ./dom/events/scrolling/scrollend-event-fired-after-sequence-of-scrolls.tentative.html - This test ensures a single user gesture that contains pauses triggers a singe scrollend event. Again, with this current webdriver APIs I'm not sure how we could implement this without a touch scroll.

The other tests do not seem to use touch scrolls.

[dlrobertson]

If limiting the tests to cases that use programmatic scrolls, would be a reasonable subset to get some form of scrollend into interop, the following tests use only programmatic scrolls:

• dom/events/scrolling/scrollend-event-fired-for-programmatic-scroll.html
• dom/events/scrolling/scrollend-event-fired-for-scrollIntoView.html

[nairnandu]

Thank you for proposing Scrollend Events for inclusion in Interop 2024.

We wanted to let you know that this proposal was not selected to be part of Interop 2024. This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year, if necessary.

For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024!

Posted on behalf of the Interop team.