| Summary: | The accept dialog after changing screen resolution is not modal and is not properly set up for operation with the keyboard | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Frank Steinmetzger <dev+kde> |
| Component: | kcm_kscreen | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | christophdreier, kde, nate, plasma-bugs-null |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 5.23.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Frank Steinmetzger
2021-11-30 19:07:31 UTC
Git commit 5ac4d7c6cbce0e9e0e2d143f531908d36201ea1b by Méven Car. Committed on 17/12/2021 at 17:27. Pushed by meven into branch 'master'. KCM: allow to use Enter/space to revert or keep new settings M +12 -0 kcm/package/contents/ui/main.qml https://invent.kde.org/plasma/kscreen/commit/5ac4d7c6cbce0e9e0e2d143f531908d36201ea1b *** Bug 451274 has been marked as a duplicate of this bug. *** Probably thanks to Méven's change, pressing enter works now (just tested on 5.24.3), but only if a button is focused. Well, that's correct of course, but getting there is another story: - None of the buttons is focused by default - focus leaves the dialog after a few presses on Tab In essence, it's something that is made to look like a dialog, while technically it is not, bringing with it the baggage to have to reimplement expected default behaviours. The tab order also is a bit weird when going back and forth with Tab/Shift+Tab: - press Tab a few times initially to reach the Accept button - press Tab again, the Accept button is still focused - press Tab once more, and now the Revert button is focused - in the other direction (with Shift+Tab) the focus stays on the Accept button for only one cycle. (In reply to Frank Steinmetzger from comment #3) > In essence, it's something that is made to look like a dialog, while > technically it is not, bringing with it the baggage to have to reimplement > expected default behaviours. An accurate assessment. This is still very much an existing bug in the current Plasma 6.4.4. I would like to nominate this for the 15-minute bug initiative, as it definitely took me less than 15 minutes before my keyboard based HTPC setup came to a complete halt while I had to pull out and connect my bluetooth mouse just for that one click. |