-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core-list scroll #748
Comments
@giltig Can you provide more background on how to repro? Which platform? When you say "pressing scroll-wheel", you mean by rolling the scroll wheel on a mouse, or something else? Thanks. |
I encountered this issue on iOS 8 (iPad, Chrome + Safari) & Android (Galaxy S3, Chrome - less severe than iOS) on a list with momentum scrolling. Specifically, the list gets stuck when you start scrolling from its top or bottom where after a split second it gets stuck. You then need to wait until the scroll indicator disappears and then it scroll fine again. |
Sure, The platform is Windows 7, Chrome 37. |
@giltig This looks like a Chrome for Windows bug with auto-scroll. I made a repro in JSBin, and attached it to an existing bug in the Chromium tracker here: https://code.google.com/p/chromium/issues/detail?id=401934. Closing the Polymer issue. |
@mavropalias The issue @giltig reported is specific to auto-scroll using a mouse-wheel, so it looks like you're reporting a different bug if it's related to touch devices. If you're still seeing a bug using today's master, can you open a new bug and be a little more specific about how it repros and exact OS & browser versions? Also, when you say "stuck", do you mean scrolling freezes (animation halts)? Or rows scroll off the page leaving white? As you described it ('have to wait until the scroll indicator comes back"), that's indicative of older platforms not sending scroll events during momentum, which core-list relies on. |
When doing auto scroll (usually by pressing the mouse wheel) the core-list scroll get stuck.
also selection is not possible anymore.
The text was updated successfully, but these errors were encountered: