Bug 445239

Summary: Scrolling changes contents of dropdowns etc. even when it shouldn't
Product: [Plasma] Breeze Reporter: Natalie Clarius <natalie_clarius>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: natalie_clarius, nate, thomas.surrel
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Natalie Clarius 2021-11-10 00:11:50 UTC
SUMMARY

Mouse wheel scrolling changes contents of dropdowns, sliders, spinboxes and the like even when it shouldn't, e.g. when scrolling the surrounding window.

STEPS TO REPRODUCE
1. Open some settings window with elements that accept input by mouse wheel.
2. Scroll the window with the cursor in a position where later down a settings element will accidentally get under the mouse cursor.

OBSERVED RESULT
The contents of the settings element unwantedly change.

EXPECTED RESULT
The scrolling doesn't change the settings, only scrolls the window.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.16-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Settings change on scrolling is very easily triggered by accident, especially when scrolling the surrounding window. This leads to unwanted changes, often without noticing, which can be very annoying (see e.g. https://www.reddit.com/r/kde/comments/9xgw29/disable_scrolling_as_dropdown_context/, https://www.reddit.com/r/kde/comments/bn0ri1/disable_scrolling_into_dropdowns_and_spinners/, https://www.reddit.com/r/kde/comments/9cbema/mouse_wheel_changes_sliders_and_drop_down_menus/, https://forum.kde.org/viewtopic.php?f=17&t=111261).

There should be an option to globally disable this feature, or at least some way of making sure it isn't triggered by accident, e.g. by accepting mouse wheel input only after the element has been clicked.
Comment 1 Nate Graham 2021-11-10 16:59:26 UTC

*** This bug has been marked as a duplicate of bug 399324 ***