Bug 419136 - On the touchpad settings page, the Apply button becomes disabled when the window state changed
Summary: On the touchpad settings page, the Apply button becomes disabled when the win...
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (other bugs)
Version First Reported In: 5.18.3
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2020-03-23 09:38 UTC by popov895
Modified: 2022-05-10 16:06 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 5.24
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description popov895 2020-03-23 09:38:40 UTC 
SUMMARY

On the touchpad settings page, the "Apply" button becomes disabled when the window state changed (e.g, maximize/restore). It looks like that the changes are reset, but UI of the page still displays these changes.

STEPS TO REPRODUCE
1. Open Touchpad KCM
2. Make some changes
3. Maximize/restore KCM window

OBSERVED RESULT

The "Apply" button becomes disabled

EXPECTED RESULT

The "Apply" button remains enabled

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: KDE Neon 5.18
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Comment 1 popov895 2020-03-23 10:01:16 UTC 
https://streamable.com/dkf9x
Comment 2 Nate Graham 2020-04-15 13:58:01 UTC 
Can reproduce.
Comment 3 Patrick Silva 2021-06-16 13:24:20 UTC 
Still reproducible on neon unstable.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.22.80
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Graphics Platform: Wayland
Comment 4 popov895 2022-04-04 19:32:22 UTC 
Looks like it's fixed for now.

Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
Graphics Platform: X11
Comment 5 Nate Graham 2022-04-04 19:46:45 UTC 
Yep, fixed for me too.
Comment 6 Nate Graham 2022-05-10 16:06:51 UTC 
*** Bug 453612 has been marked as a duplicate of this bug. ***