1831893 - [KDE] Support high-res scroll on Wayland (wl_pointer.axis_value120)

Status: NEW

(Core :: Widget: Gtk, enhancement, P3)

Description

[[object Object]]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0

Steps to reproduce:

Scrolled with a high-res scroll wheel on Firefox running on Wayland

Actual results:

High-res scroll events

Expected results:

High-res scrolling used to work fine, but since this bugfix, it doesn't, because firefox doesn't support receiving high-res scroll events on wayland (wl_pointer.axis_v120).

I'm compiling my own version of kwin to revert the above commit, and high-res scrolling already works fine, so it should just be a matter of advertising support for the protocol..? I don't know very much about Wayland

Comment 1

[Daniel Bodea [:danibodea]]

Verifying that this is an improvement rather than a flaw, it's important to note that reproducing or investigating it requires a specialized mouse. Additionally, the individual who reported this implies that it's a recurrence within kwin/wayland, making it distinct from a regression issue in Firefox.

Comment 2

[[object Object]]

(In reply to Daniel Bodea [:danibodea] from comment #1)

Verifying that this is an improvement rather than a flaw, it's important to note that reproducing or investigating it requires a specialized mouse. Additionally, the individual who reported this implies that it's a recurrence within kwin/wayland, making it distinct from a regression issue in Firefox.

As I understand it, previously KDE was sending hi-res pointer events to every window, no matter if they advertised support for the protocol or not. This was causing issues in some apps that were not built for hi-res scroll, so they had to limit it to just apps that advertise support.

If potential fixes are put in nightly builds, I could test them (as I use one of said specialized mice).

Comment 3

[[object Object]]

*hi-res scroll events not pointer events

Comment 4

[[object Object]]

Looking at the KWIN code more closely, it seems like might need to update your Wayland protocol version…? This documentation shows that the wl_pointer::axis_value120 event has been around since version 8, but I'm not sure what that means exactly.