Many User Settings give no indication of which is the active choice

Jon wrote in post #17824266
Yes, but only the active option has the underline. And the purple customarily indicates a previously-followed link, so . . .

I'll try to explain my point better. I find the current typography counterintuitive because the active option has the underline. The inactive option is plain black. On typical Web pages, if you want to do something, such as go to another page or change a current setting, you click some text that's colored, underlined, or both. Plain black text usually isn't clickable. In FYEO, however, the reverse is true.

My settings are: allow PMs and do not send notifications. Screenshot:

HOSTED PHOTO
please log in to view hosted photos in full size.

Pekka wrote in post #17824021
Yes, I have planned to improve clarity of the settings. Whether it is radio button or something else needs to be determined.

But what is this ranting and negativity, BEFORE I even answered the post??

If you really work for AI design, perhaps you own algorithms on how to present and discuss feature requests would need some updating.

The "Ranting and negativity" were replies to other user's comments. It was a trivial issue of a kind that is extremely easy to overlook as a developer because larger and more important issues tend to push that kind of thing down to the bottom of the pile, if it was ever actually considered by the development team, and couldn't find anything about it. Then a few users tried to defend the design?

The design is ambiguous: nothing defines the colours or clearly states the meaning of how it works, and as binary choices they could just as easily go either way.
This is horrible for a UI because it fails to do its job: Communicate to the user what the settings are.

If anyone disagrees with this view, then that is their choice, but I really hope they never have anything to do with UI design on something I end up having to use a lot.

At work I'm paid to be blunt and solve problems, I'm not paid to sugar coat things or stroke other developer's egos.

Luckless wrote in post #17824934
The design is ambiguous: nothing defines the colours or clearly states the meaning of how it works, and as binary choices they could just as easily go either way.
This is horrible for a UI because it fails to do its job: Communicate to the user what the settings are.

I agree that the state of a setting can be misunderstood. But, at the moment you first time actually click an option to choose it, it becomes undeniably clear how the coloring + underline vs. plain black works. Nevertheless, I'll make it better, but it is not first priority job at the moment.