Closed Bug 1498685 Opened 6 years ago Closed 6 years ago

scroll-behavior: smooth on Chrome can cause motion sickness issues

Categories

(developer.mozilla.org Graveyard :: Design, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sheppy, Assigned: espressive)

References

Details

(Keywords: in-triage)

According to a user today in IRC, he gets motion sickness issues from the smooth scrolling implementation by Chrome when using the find-in-page functionality -- especially when it zooms from the end of the page back to the top when the search wraps back to the top of the page.

I've recommended that the user file a ticket with Google about this issue, but we may wish to consider whether or not we should make changes to alleviate this potential issue, if we feel that it's significant enough to justify taking action.
Also: https://discourse.mozilla.org/t/scrolling-behavior-on-mdn/32564

This was introduced by the fix for bug 1479817. I'm not sure if smooth scrolling was necessary for the solution.
See Also: → 1479817
Assignee: nobody → schalk.neethling.bugs
Status: NEW → ASSIGNED
:sheppy :jwhitlock I was actually worried about that, but see it so much across many sites I thought it might be ok. Should have trusted my gut. I am opening I PR to stop that from happening, and just have it jump.
Firefox's implementation of it is vastly better. Thought I would mention it here ;)
Keywords: in-triage
Priority: -- → P1
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/df94d052f7d6edefa6c058e5d2a3d7a12a517dd9
Bug 1498685, remove smooth scrolling

https://github.com/mozilla/kuma/commit/b821fb80a7c25623a331d918215e21ec16d01639
Merge pull request #5038 from schalkneethling/bug1498685-remove-smooth-scroll

Bug 1498685, remove smooth scrolling
This shipped around 2018-10-15, I'm not aware of further complaints.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.