https://bugs.kde.org/show_bug.cgi?id=485073
Bug ID: 485073 Summary: Kirigami.Action doesn't honor KeyNavigation.tab Classification: Frameworks and Libraries Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: albertv...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided Context: I'm trying to fix the fact that pressing "tab" in the KDE Connect app walks the buttons backwards. I originally reported this in https://bugs.kde.org/show_bug.cgi?id=482752 but was told that this should be fixed per-app and not in Kirigami. I found that Qt supports KeyNavigation.tab [1] to indicate, for each element, which is the next element to be selected when tab is pressed, together with KeyNavigation.right and KeyNavigation.left for the arrow keys. Although I still think that tab navigation should work out of the box, KeyNavigation seemed like a way to (with a bit of hardcoding) fix it for KDE Connect at least. However, when I tried it, I found that KeyNavigation.tab makes no difference when I use it in a Kirigami.Action. Does Kirigami.Action not support KeyNavigation.tab? [1] https://doc.qt.io/qt-6.5/qml-qtquick-keynavigation.html#tab-attached-prop -- You are receiving this mail because: You are watching all bug changes.