New issue
Advanced search Search tips

Issue 817129 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 778259
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

[scroll-snap] physics feel unintuitive/intrusive compared to rest of web/app landscape

Reported by h...@jonjohnjohnson.com, Feb 27 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3356.0 Safari/537.36

Steps to reproduce the problem:
1. Go to this url -> http://output.jsbin.com/subojom/9
2. Notice how intrusive 'snapping' feels compared to movement during scroll inertia.
3. Check out feeling of scrolling/snapping in other environments, both native (Android/iOS) and safari's implementation of [scroll-snap] to compare.

Though the spec [https://www.w3.org/TR/css-scroll-snap-1/] doesn't explicitly say how the physics must feel, I am guessing developers using these new properties would be deterred when seeing the behavior in blink compared to others. Also, I may be jumping the gun in critiquing a feature that's not quite finished yet, but hoping the final outcome feels much better.

Video of Chrome Canary 66 -> http://cl.ly/poy9
Video of Safari 11 -> http://cl.ly/pq0s

What is the expected behavior?
At the end of the users gesture the final snap-position would be analyzed and animated to smoothly (based upon current speed/direction of scroll).

What went wrong?
At the end of scroll gesture, normal inertial scrolling commences, slowing down until almost stopping, then scroll-snap position seems to be taken into account and scrolling speeds up (possibly changing direction) and eventually stops.

Did this work before? N/A 

Chrome version: 66.0.3356.0  Channel: canary
OS Version: OS X 10.12.6
Flash Version:
 

Comment 1 by ajha@chromium.org, Feb 28 2018

Labels: Needs-Triage-M66
Components: Blink>Scroll
Labels: Triaged-ET M-66 FoundIn-66 Target-66 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #66.0.3356.0.
This is a non-regression issue as it is observed from M60 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!

Comment 3 by bokan@chromium.org, Mar 1 2018

Cc: bokan@chromium.org majidvp@chromium.org
Owner: sunyunjia@chromium.org
Status: Assigned (was: Untriaged)
Mergedinto: 778259
Status: Duplicate (was: Assigned)
Thanks for the feedback! We are actively working on this feature right now :)
Just saw the update on the duplicate of this issue, and it feels wayyyy better! Good job!
https://bugs.chromium.org/p/chromium/issues/detail?id=778259

But, it's still not scrolling/snapping to what would "feel" like the correct snap position, often when scrolling downwards in the example link provided.

http://output.jsbin.com/subojom/9

Can you see the times where it snaps back upward when clearly feeling like it should have the velocity/direction to snap to the next position?

Looks like it's sometimes even skipping the position in the wrong direction and going beyond to the next?
Thanks for trying! This feature hasn't been fully finished yet and we have a lot of code to land. Please wait until the  crbug.com/778259  has been marked as Fixed.

Sign in to add a comment