If you’re genuinely asking… the yes option. But that is indeed a shitty ass UI.
My answer comes from the “thumb print” effect - that radial shadow pattern is supposed to remind the user of their finger partially blocking the light on an illuminated button.
I think the radial shadow pattern is actually supposed to evoke the edges of the hollow in which the button is depressed, but otherwise I agree with you 100%.
Also the “no” has the yellow reflection from the graphic above, implying its projecting out.
✨affordances!✨
You should post this in the group assholedesign. This is genuinely so bad it’s infuriating.
Kind of more crappydesign than assholedesign, but yes.
“yes” is selected, it looks pressed in
Good UI is severely underrated, and it makes you somehow feel dumb when it’s bad.
Are you sure you want to cancel?
- Cancel
- Continue
How anyone developing an interface thinks that is a good idea is beyond me, but I am convinced they are doing multiple lines every morning.
Not a great UI but honestly the yes looks pressed in the 3d meaning of the word.
So it’s not terrible
Funny. I thought the No was selected
I think that might be because modern UI tends to move away from 3d and insted highlights the selected button (making it lighter in color)
Yeah I think that’s the problem here. Older uis leant into the faux 3d thing whereas modern designs are mostly flat/minimal
Bring back skeumorphism
Oh god no! =)
The “yes” is selected.
To me is the yes since it has a different color than the window it comes in.
Press left. If nothing changes, then Yes is selected.
You’d be surprised how many shitty UIs x-wrap navigation when there are only two options.
Is the play here to always make sure there are at least three options anywhere?
Sadly keep pressing left they just cycle back and forth
Fucking of course. Leave it to such a dev to ensure no logical method can work the problem.
Easy, you just press right and see if the option moves.
Oh wait that just toggles between them. I’ve never used whatever this is, but you know it does.
Actually I had to guess as to the correct answer was. I guessed wrong and the movie started over
It’s been at least 3 hours now. Which was it?
I had the yes set to white and the movie started over.
Oh no! Guessing you wanted to resume?
Yup. But at least I had set a bookmark. Although the interface for selecting a bookmark isn’t any better.
The one that always gets me is GNOME’s screen sharing portal.
There is this outline around the “Application Window” tab which makes it seem selected. I use this UI multiple times a week and I need to pause for a sec every single time. I always think “I want to share a window”, “oh it is already selected” then stare at the monitors for a while before I realize why I can’t understand what I am looking at.
If they did the exact opposite of this, I think it would look ok. If I was trying to fix this, I would probably just swap the styles of the selected and deselected states. Maybe it’s a miscommunication between designers and implementers, causing the meanings to be swapped?
I don’t think it is that simple. I think that outline is about the “focus”. So if I press enter it will activate that tab, if I press tab it will move the focus to the “Entire Screen” tab.
The UX issue is that there are two concepts of focus in this UI. There is “which tab is active” and “what UI element will pressing enter activate”. These two are not sufficiently differentiated which leads to a confusing experience.
Or maybe there can just be no keyboard focus indicator by default, but that may be annoying for keyboard power users. But this is generally how it works on the web, you have to press tab once to move keyboard focus to the first interactive element.
Right, that makes sense as well. What I was thinking is that the use of the accent colour shows which one is active, though it would probably be less confusing if this wasn’t done with an outline. See the KDE version for example:
Regarding keyboard navigation, I could see this working similarly to radio buttons, where the tab key selects the entire tab group, and tabs need to be navigated using the arrow keys. In this case I think it makes sense to put the focus border around only the selected option, and having the focus border follow the selected option when arrow keys are used. If this is the case, I think swapping the current version does make sense.
Yeah. I like old school tabs that were clearly attached to the thing that they switched. I definitely prefer the KDE UX here.
Sadly KDE is also trying out the “modern” style tabs in some places too:
I’m failing to think of a use case for separation of what has focus and what will be activated when hitting enter. Seems like something an insane person would come up with.
The same use case why moving your mouse across a tab doesn’t focus it? It is important to have a difference between the current focus of actions and the state of each individual UI element. Keyboard users will want to be able to move their focus across the tabs without switching which one is active.
y e s
I hate those widgets! I’ve had this exact problem many times before
I’d say yes, but I did have to look at it closely. Plus the assumption that it would probably default to continuing.
