The change is not in the configured time window. Rubber Stamper is only allowed to review reverts within 14 day(s). Learn more: go/rubber-stamper-user-guide.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Revert "Fix touchpad scroll sensitivity on Wayland."
This reverts commit ded09f2a729ad7d92f404bd9f86fac819f178f8b.
Reason for revert: Users found the slower scroll speed relative to other Wayland applications to be disruptive.
Original change's description:
> Fix touchpad scroll sensitivity on Wayland.
>
> Chrome's scroll sensitivity with a touchpad is much higher on Wayland
> than on other OSes. Chrome isn't alone in this--Terminal and several
> other applications also scroll much faster than I'd expect--but one
> notable exception is the "Test settings" page of the touchpad
> configuration UI, the scroll sensitivity of which feels comparable to
> using a touchpad on other OSes.
>
> I believe that axis events coming via `OnAxis` should not be scaled at
> all. That feels right when using a physical touchpad, but more
> importantly, if `ei_device_scroll_delta` is used to inject scroll
> events, the magnitude of those events is specified in pixels. The
> comment in `OnAxis` (that this CL deletes) mentioned wheel ticks, but
> this CL doesn't affect wheel ticks at all, since they are delivered via
> `OnAxis120`, which takes precedence.
>
> My ultimate goal is to have CRD host use `ei_device_scroll_delta` so
> that we can support smooth scrolling. It's not currently possible due
> to https://gitlab.freedesktop.org/libinput/libei/-/issues/88, but this
> CL is a prerequisite. In particular, if the `OnAxis120` implementation
> is removed in addition to this CL, then I can get the scroll distances
> to match on client and host when Chrome Wayland is used at both ends.
> Without this CL, Chrome running on the host scrolls 144 times too far
> due to scroll distances being multiplied by 12 by Chrome at both ends.
>
> Change-Id: Id576c3a10e3dc1847ab278502b31baf51592ce55
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7004208
> Commit-Queue: Thomas Anderson <thomasa...@chromium.org>
> Reviewed-by: Thomas Anderson <thomasa...@chromium.org>
> Auto-Submit: Jamie Walch <jamie...@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1524565}
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |