Bug 471957 - Apply button is not in the tab order when viewing QML KCMs
Summary: Apply button is not in the tab order when viewing QML KCMs
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.27.6
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: accessibility, usability
: 443522 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-07-04 19:38 UTC by jonzn4SUSE
Modified: 2024-03-25 01:49 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jonzn4SUSE 2023-07-04 19:38:00 UTC
SUMMARY
When tabbing through the Touchpad page in System Settings, the Apply button in not part of the tab order.
After tabbing to Device enabled and hitting the space bar, I wanted to tab down to the Apply button to enable the Touchpad, but tab focus just goes back to the top option Device enabled.  

STEPS TO REPRODUCE
1. Go to System Settings >>> Input Devices >>> Touchpad
2. Then check the box for Device enabled
3. Using the Tab key, try to tab down the Apply button, but the button is not part of the tab order.  It just back to the top option Device enabled.

OBSERVED RESULT
The Apply button is not in the tab order

EXPECTED RESULT
Should've been able the Apply button using the tab key

Operating System: openSUSE Tumbleweed 20230629
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.9-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics
Memory: 62.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: HP
Product Name: HP ProBook 455 15.6 inch G9 Notebook PC

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-09-13 18:32:46 UTC
Yeah, for now you'll need to use the Alt key accelerators to access the buttons on the bottom.
Comment 2 Nate Graham 2024-03-25 01:49:22 UTC
*** Bug 443522 has been marked as a duplicate of this bug. ***