New issue
Advanced search Search tips

Issue 769390 link

Starred by 6 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-11-30
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression

Blocked on:
issue 249063



Sign in to add a comment

Unable to scroll in “virtualscroll”-tables (e.g. SlickGrid.js) when using the mousewheel-click technique (click once then drag mouse in any direction)

Reported by hbe...@gmx.net, Sep 27 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:
When using the mousewheel-button to scroll a "virtualscroll"-table, the scrolling reliably just stops after about a second. This only happens in Chrome's latest build (61.0.3163.100), it definitely did not happen before.
Normal scrolling by just turning the mousewheel or using the scrollbars works as expected.

I'll provide a link to a SlickGrid Demo to illustrate the problem, although this is not a SlickGrid-specific problem. I noticed this behaviour with other such libraries as well: http://mleibman.github.io/SlickGrid/examples/example3-editing.html

What is the expected behavior?
Scrolling should continue until the mouse is clicked again, or the end of the table is reached of course.

What went wrong?
---

Did this work before? Yes 60.0.3112

Chrome version: 61.0.3163.100  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 

Comment 1 by woxxom@gmail.com, Sep 27 2017

Bisect info: 479929 (good) - 479932 (bad)
https://chromium.googlesource.com/chromium/src/+log/0c7f6df4..94354e4b?pretty=fuller
Suspecting r479931 "Move middle-click autoscroll to synthetic fling"
Landed in 61.0.3133.0
Cc: pbomm...@chromium.org bokan@chromium.org
Components: -Blink Blink>Scroll
Labels: M-61 OS-Linux OS-Mac
Owner: aelias@chromium.org
Status: Assigned (was: Unconfirmed)
Based on comment#1 assigning to the CL owner.



I can confirm this issue. It looks like scrolling stops as soon as the element, that was under the cursor at the start of scrolling, leaves the viewport.

Comment 4 Deleted

Comment 5 Deleted

Comment 6 by jeff...@roll20.net, Oct 23 2017

Suspecting whatever caused this regression is also affecting users of Chrome on Roll20; middle-click does not pan the viewport on the Virtual Tabletop. Admittedly, the VTT is a somewhat complex beast but it does not fiddle with scroll events too much.  You might choose to use this as another test-case.

I've confirmed that previous versions of Chromium do not have the issue; the last that worked was the build that would become Chrome 60 Stable.

Thanks!

Comment 7 by aelias@chromium.org, Oct 27 2017

Owner: ----
Status: Available (was: Assigned)

Comment 8 by bokan@chromium.org, Oct 27 2017

Status: Untriaged (was: Available)
Marking untriaged so we take a look during triage period.

Comment 9 by bokan@chromium.org, Nov 16 2017

Labels: Needs-Feedback
NextAction: 2017-11-30
I can't repro on the given example in 62.0.3202.94 and I recall we fixed some bugs regarding virtual scrollers like this recently - I suspect it might have been fixed. Could you retry in an updated Chrome version? (or Canary channel)

Comment 10 by hbe...@gmx.net, Nov 16 2017

I can still reproduce the issue in Chrome 62.0.3202.94 (official build, 64-Bit, Windows 7). Example used: http://mleibman.github.io/SlickGrid/examples/example3-editing.html
Scrolling stops as soon as the scrolled/latched node is removed from the DOM.

Comment 11 by sahel@chromium.org, Nov 23 2017

Blockedon: 249063
Owner: sahel@chromium.org
Status: Assigned (was: Untriaged)
Autoscroll with click is implemented by handling fling. With virtual scroll table when the target element gets removed we must transfer the fling curve to the main thread, which currently only happens for touchpad fling.

Browser side fling for autoscroll will solve the issue.
The NextAction date has arrived: 2017-11-30

Sign in to add a comment