4 ms·

Awful UX. The “one of more” component is exactly a list of checkboxes followed by a “confirm selection” button that warns you when nothing is selected. The co

by sureIy 2y ago

Awful UX. The “one of more” component is exactly a list of checkboxes followed by a “confirm selection” button that warns you when nothing is selected. The constraints is enforce at the time of submission. Even in real life, when talking to a human who wants one or more words to continue, you won’t be able to continue without giving one or more words.

stby 2y ago
In fairness, the article comes to the same conclusion.
n4r9 2y ago
> The “one of [sic] more” component is exactly a list of checkboxes followed by a “confirm selection” button that warns you when nothing is selected. > The constraints is enforce [sic] at the time of submission. Perhaps it would be better to have all items selected initially. The user deselects those that they do not want. If they try to deselect everything then they get a warning popup at that point.
- layer8 2y ago
  No. The GP is no different from a mandatory field. You can have a default value set, but then that should be a value that makes a good default for every user.
  - chatmasta 2y ago
    Multi-select or not, for inputs like language or region selection, there can be 200+ options. I think that’s why some form designers try to make a “best guess” at moving common options to the top. This frequently leads to annoyances like scrolling to the bottom only to say “where’s United Kingdom?”
    - layer8 2y ago
      This doesn't have anything to do with the context of this thread, but it's possible to have the same option at the top and also at its sorted position.
straws 2y ago
The convention on desktop and mobile is not to have a submission at all. If you click one of these "mercury" buttons, you can always have up-to-date state. Forms and submissions are mostly a web convention. I too think that's more natural, but there are a lot of existing contexts like settings where the expectation is that making the selection doesn't require an explicit "save" step.
- SebastianKra 2y ago
  That's a bad excuse. There are plenty of widgets that need to deal with illegal states in an auto-saving form. For example, every text input that expects a numeric value needs to allow an empty string. If you don't want to deal with validation logic in your app, you could just disable the last checkbox.
  - sureIy 2y ago
    I like your last point. Also in practice this state does not happen in “apps”. Before the user reaches the screen, you must have set a default. If you have default, then “deselect all” will eventually revert to that default.
layer8 2y ago
It’s exactly like a mandatory field. You wouldn’t want a mandatory text field to insert a random string when you clear it (or have a random string as its initial value), just to maintain the invariant that it must not be blank. In a similar vein, a set of radio buttons can be initially unselected, in order to force a user selection, even though only selected states are valid states.

by sureIy 2y ago

stby 2y ago

In fairness, the article comes to the same conclusion.

n4r9 2y ago

> The “one of [sic] more” component is exactly a list of checkboxes followed by a “confirm selection” button that warns you when nothing is selected. > The constraints is enforce [sic] at the time of submission. Perhaps it would be better to have all items selected initially. The user deselects those that they do not want. If they try to deselect everything then they get a warning popup at that point.

layer8 2y ago
No. The GP is no different from a mandatory field. You can have a default value set, but then that should be a value that makes a good default for every user.
- chatmasta 2y ago
  Multi-select or not, for inputs like language or region selection, there can be 200+ options. I think that’s why some form designers try to make a “best guess” at moving common options to the top. This frequently leads to annoyances like scrolling to the bottom only to say “where’s United Kingdom?”
  - layer8 2y ago
    This doesn't have anything to do with the context of this thread, but it's possible to have the same option at the top and also at its sorted position.

straws 2y ago

The convention on desktop and mobile is not to have a submission at all. If you click one of these "mercury" buttons, you can always have up-to-date state. Forms and submissions are mostly a web convention. I too think that's more natural, but there are a lot of existing contexts like settings where the expectation is that making the selection doesn't require an explicit "save" step.

SebastianKra 2y ago
That's a bad excuse. There are plenty of widgets that need to deal with illegal states in an auto-saving form. For example, every text input that expects a numeric value needs to allow an empty string. If you don't want to deal with validation logic in your app, you could just disable the last checkbox.
- sureIy 2y ago
  I like your last point. Also in practice this state does not happen in “apps”. Before the user reaches the screen, you must have set a default. If you have default, then “deselect all” will eventually revert to that default.

layer8 2y ago

It’s exactly like a mandatory field. You wouldn’t want a mandatory text field to insert a random string when you clear it (or have a random string as its initial value), just to maintain the invariant that it must not be blank. In a similar vein, a set of radio buttons can be initially unselected, in order to force a user selection, even though only selected states are valid states.