|Summary:||Default buttons are almost indistinguishable from other buttons when not focused|
|Product:||[Plasma] Breeze||Reporter:||Nate Graham <nate>|
|Component:||QStyle||Assignee:||Hugo Pereira Da Costa <hugo.pereira.da.costa>|
|Latest Commit:||Version Fixed In:|
|Attachments:||Default button almost indistinguishable from other buttons|
Description Nate Graham 2017-10-24 22:49:59 UTC
Comment 1 Albert Astals Cid 2017-10-24 23:06:02 UTC
I don't think blue is the right color, blue is the color for the focused button. Also https://phabricator.kde.org/D7828 is *not* a generic workaround, it only workarounds messageboxes, not the rest of different dialogs
Comment 2 Nate Graham 2017-10-24 23:09:39 UTC
Sure, it doesn't have to be dark blue like focused buttons. Maybe a lighter blue, or a heavier weight outline, or something else.
Comment 3 Hugo Pereira Da Costa 2017-10-29 09:56:34 UTC
I disagree that the default buttons should be made more prominent. I consider hitting the return key in the dialog rather than using the mouse or the tab key to change focus an advanced user feature, in which case it should not be an issue, the first time at least, to spend the extra second needed to find which button is the default. In doubt, one can always use the tab keys. On the other hand making it more prominent would rather clutter the UI for a somewhat limited use. It would also increase the confusion (to non advance users) between the widget that has focus and the default button (as of today I am not even clear which one, and in which case, takes precedence on the second). Also, when using a dialog which have buttons beside the one from the button box and switching focus using eg tab key (see for instance oxygen-demo5, buttons tab), see how the default button highlight comes on and off depending on the nature of the widget that has focus. This blinking behavior would become even more annoying/confusing if the default button was to be made more prominent. Last but not least: this "issue" (or absence thereoff) was already discussed some several years ago and no better design was found at that time (and as far as I know, still none today). Wont fix. Sorry.
Comment 4 Nate Graham 2019-10-07 15:47:59 UTC
*** This bug has been marked as a duplicate of bug 364226 ***