[csswg-drafts] [css-om-view] Should overscroll ("rubber-banding") be observable? (#4011)

smfr has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-om-view] Should overscroll ("rubber-banding") be observable? ==
https://www.w3.org/TR/cssom-view-1/#scrolling-events doesn't say anything about whether a UA should fire scroll events when the user triggers overscroll behavior (https://drafts.csswg.org/css-overscroll/) and the visual scroll offset becomes negative.

WebKit has traditionally allowed negative scrollTop/scrollLeft to be observable by web content, but many pages are obviously not prepared to handle negative values (e.g. CodeMirror's gutter contents jiggle around, Quip does weird things etc). And the UI behavior that triggers negative values is an Apple-specific ones; other platforms like Android don't move the content to negative offsets, but rather show an overlapping UI affordance.

Yet some authors want to tie into overscroll behavior to implement behaviors like pull-to-refresh.

So perhaps we need a new event for overscroll interactions ("overscroll"?)

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4011 using your GitHub account

Received on Thursday, 6 June 2019 02:06:17 UTC