https://bugs.kde.org/show_bug.cgi?id=384514
Bug ID: 384514
Summary: Pushbuttons, Toggle Buttons, and Segmented Controls
look nearly or actually identical to one another
Product: Breeze
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-devel@kde.org
Reporter: pointedst...@zoho.com
Target Milestone: ---
There are a few usability problems with toolbar buttons in Breeze stemming from
the fact that multiple types of controls have the same visual appearance. For
example, consider this standard toolbar in Gwenview. Here's what the user sees:
https://i.imgur.com/Nu3WieQ.png
The darkened background acts as a visual cue that that the "View" button has a
toggle-able state. But the rest all look like regular pushbuttons.
However, here's what they actually are: https://i.imgur.com/eAVm9Wk.png
You can see that the View toggle button is not actually a toggle button at all
but rather part of a segmented control with browse button, expressing the idea
that only one state can be active at once: Browse or View. But this isn't
obvious because those two buttons aren't grouped together in any wya that
suggests that only one state at a time is active.
Meanwhile, the Sidebar button is actually a toggle button rather than a regular
pushbutton, even it looks the same as the Full Screen button next to it, which
is a regular pushbutton.
We should consider doing the following:
- Tweak the un-toggled state of toggle buttons to differentiate them from
pushbuttons
- Visually connect the buttons together in segmented controls to differentiate
them from toggle buttons and pushbuttons
For reference, here's the Apple HIG on the matter:
- Segmented controls:
https://developer.apple.com/macos/human-interface-guidelines/selectors/segmented-controls/
- Pushbuttons:
https://developer.apple.com/macos/human-interface-guidelines/buttons/push-buttons/
Notice that these UI elements can be easily distinguished from one another
visually.
--
You are receiving this mail because:
You are the assignee for the bug.
