SUMMARY I do not use scroll this way, and never will. I expect my scroll to scroll the actual page and not to randomly change some values in settings just because I aimed my mouse at the wrong spot. This is especially annoying in, for example, tray settings, where the dropdowns take a major part of the frame. I'm not the only one annoyed by this "feature": https://www.reddit.com/r/kde/comments/bn0ri1/disable_scrolling_into_dropdowns_and_spinners/ https://www.reddit.com/r/kde/comments/9xgw29/disable_scrolling_as_dropdown_context/ https://www.reddit.com/r/kde/comments/rb9rhk/undesired_behavior_turn_off_mouse_scroll_changing/ https://bugs.kde.org/show_bug.cgi?id=385270 In the other bug report and one of the posts, this (https://invent.kde.org/frameworks/kirigami/-/merge_requests/415) was mentioned as a "fix", when the real fix people actually want is to completely disable this "feature". The other bug report was also aimed to sliders specifically, while they also can be a bit annoying, my main issue are dropdowns. If with sliders I can see how this would be useful, with dropdowns you can't even see the next or previous value, so basically you're just blindly scrolling through each value trying to find the one you need. While this may be somewhat useful with dropdowns that have just a couple of values, more often it's just an annoying and unwanted behavior I think the best place to put this setting in is the Quick Settings, aka the starting page of Settings. With kind regards, pls fix. STEPS TO REPRODUCE 1. Scroll with mouse wheel on some dropdown or slider in Plasma settings SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor 1: AMD Radeon Graphics Graphics Processor 2: NVIDIA GeForce RTX 3060 Laptop GPU ADDITIONAL INFORMATION
Thanks for the bug report! This is a long-standing issue that is unfortunately not trivial to fix consistently. I'm marking this as a duplicate of the main bug where this is discussed, even if the proposed solution there isn't quite what you suggest here. Feel free to add your argument for your solution to that bug report. *** This bug has been marked as a duplicate of bug 399324 *** *** This bug has been marked as a duplicate of bug 399324 ***
> even if the proposed > solution there isn't quite what you suggest here. If I understand correctly, the proposed solution there is "(only do the thing) if field has keyboard focus AND cursor is on top" and I think it's pretty good and will fix the annoyance in 99% cases. Thanks for you time.