Two-finger scrolling a "scrollable area" fails if first trying to scroll past limit |
|||
Issue descriptionChrome Version: 69.0.3473.0 Chrome OS Version: 10820.0.0 Chrome OS Platform: grunt Steps To Reproduce: (1) http://news.google.com (2) trying scrolling the middle box "up" (3) then without lifting fingers, try scrolling it down Expected Result: Nothing when scrolling up, content starts to move when scrolling down. Actual Result: Nothing when scrolling up, content still does not scroll when switching scroll direction to down. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always. What is the impact to the user, and is there a workaround? If so, what is it? scrolling appears flakey. See b/111252603 for videos and more details.
,
Jul 27
,
Jul 30
I can also repro this on a Mac. This is the latching behavior at work, we latch to whatever element scrolls on the first scroll event. It works on the main page because if we don't scroll at all we latch to the viewport (so that overscroll glow/rubber-banding works). Sahel, any ideas on how we might make this feel better? Perhaps we should only latch to the viewport if it has overflow and try retargetting the latch otherwise?
,
Jul 30
While scrolling by wheel (timer based latching) if all the GSUs in the current scroll sequence have been ignored so far, and the next wheel event has different delta directions we end the current scroll sequence and start a new one. We can implement something similar for scrolling by touchpad. |
|||
►
Sign in to add a comment |
|||
Comment 1 by afakhry@chromium.org
, Jul 20