There's no focus indicator on buttons when using Breeze/Breeze-Dark GTK2 or GTK3 themes, making using the keyboard to navigate a bit difficult. Focus indicators are visible when using Adwaita or Arc, and the focus highlight for the QtStyle works, so it's specific to the gtk styles. Reproducible: Always Steps to Reproduce: 1. Open gtk3-demos, and then run the button boxes demo. 2. Use the [Tab] key to move around the buttons. Actual Results: No focus indicator to see what button will be pressed when pressing [Space] or [Enter] Expected Results: Expect to see some kind of focus indicator (An underline or highlight would stylistically match the breeze qtstyle) to see what button will be pressed when pressing [Space] or [Enter].
This was fixed in https://cgit.kde.org/breeze-gtk.git/commit/?id=22637c221ee34694ddb18f7c0ec177a0da3b3dce
Created attachment 181115 [details] Focus indicators in Gimp with the Breeze theme. Can you tell, that the OK button is highlighted? By contrast, the highlighting of the "Defaults" button in the System Settings dialog is very easy to sp More specifically, it looks like the GTK breeze theme highlights the focused element very conservatively compared to the QT breeze theme. In the GTK breeze theme, the focus indicator is restricted to a very minor change in the shading of the background of elements. When you look closely you notice the c h a n g e when pressing TAB. But it took some testing to realize, that there IS any form of focus indicator. By contrast, the QT breeze theme uses sublte, but well visible, blue underlining for checkbox text, and blue drop shadows for focused buttons and dropdown lists. For buttons, additionally the button color becomes blueish. As a consequence, the focus indicators are not only hard to see in the GTK theme, but also entirely inconsistent between QT and GTK applications.
(In reply to Nate Graham from comment #1) > This was fixed in > https://cgit.kde.org/breeze-gtk.git/commit/ > ?id=22637c221ee34694ddb18f7c0ec177a0da3b3dce Sorry, a bit over-tired, so I didn't see the fix comment. But the point would be, if it was fixed, then it wasn't fixed fully. See attachment above.