https://bugs.kde.org/show_bug.cgi?id=465742
--- Comment #6 from [object Object] <objekt-obj...@proton.me> --- (In reply to Vlad Zahorodnii from comment #5) > (In reply to [object Object] from comment #4) > > Also, it did work on 5.26.90 so the regression occurred after that > > high resolution scrolling requires both compositor _and_ client support. > Most native wayland clients in the wild don't support > wl_pointer.axis_value120, so kwin sends lores scrolling to keep the > compatibility. > > This requires toolkit changes. Not sure about GTK but Qt should support high > resolution scrolling on wayland in 6.5 > https://codereview.qt-project.org/c/qt/qtwayland/+/439967 Then those clients include firefox and every qt/gtk app I've tried, effectively preventing me from using high-res scrolling at all. Having a couple clients scroll extremely fast seems like the better alternative to having high-res scroll disabled everywhere, imo the change should be reverted or there should be an option to turn it on/off then -- You are receiving this mail because: You are watching all bug changes.
