| 2018-01-31 19:19:38 |
Matthew Paul Thomas |
description |
<https://dashboard.snapcraft.io/dev/account/> begins with three disabled fields: “Full name”, “Ubuntu One email”, and “Snap account-id”.
The frustration is increased by the fields changing appearance on hover (getting a black border), but also changing the cursor to a “no entry” sign.
In general, a disabled control should be used when there is something the user could reasonably do to enable it — for example, by checking a checkbox, going online, or waiting five minutes.
Here, there is apparently nothing the user can do to enable any of the fields. So they should not be disabled; they should not be fields at all. They should be just static text. |
<https://dashboard.snapcraft.io/dev/account/> begins with three disabled fields: “Full name”, “Ubuntu One email”, and “Snap account-id”.
The frustration is increased by the fields changing appearance on hover (getting a black border), suggesting that they might be interactive, but then also changing the cursor to a “no entry” sign.
In general, a disabled control should be used when there is something the user could reasonably do to enable it — for example, by checking a checkbox, going online, or waiting five minutes.
Here, there is apparently nothing the user can do to enable any of the fields. So they should not be disabled; they should not be fields at all. They should be just static text. |
|
