Here's my new proposal (Screenshot 1 out of 3). Jörg and reporter are right, recpient delete button shouldn't appear out of nowhere from underneath when clicking recipient type selector, which is undiscoverable, unexpected, and error-prone. As discussed in bug 110103, we also don't want to clutter the entire recipient area with dozens of permanent delete buttons. In fact, even the permanent recipient type selectors are pretty noisy (over-salient) considering that users will typically use them maximally once per each recipient, and after changing the type, the dropdown then becomes irrelevant. There's absolutely no point of permanently having multiple dropdown markers for each recipient on screen. This is 2019 and ux-minimalism has long been part of best practice on any type of application or online presentation. Users know (not least from their Android phones) that they have to touch (tap/hover/focus) any element on the screen first in order to get at contextual actions, and that non-contextual/inapplicable actions are typically hidden to avoid clutter. PROPOSAL So I suggest to radically simplify/de-clutter both the recipient type selectors and the delete buttons by making them contextual, i.e. showing them only and exactly when they are needed. Ironically, this actually makes both of them MORE discoverable. 1) show recipient type selector and delete button only when applicable - when editing a recipient (this is a great way of assisting ux-discovery) - when hovering / focusing any part of a recipient row (name/type/delete) 2) hide all recipient type selector stylings (dropdown arrow, border box) when they are not applicable (i.e. when recipient is neither being edited nor hovered nor focused).
Bug 1493158 Comment 33 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Here's my new proposal (Screenshot 1 out of 3). Jörg and reporter are right, recpient delete button shouldn't appear out of nowhere from underneath when clicking recipient type selector, which is undiscoverable, unexpected, and error-prone. As discussed in bug 110103, we also don't want to clutter the entire recipient area with dozens of permanent delete buttons. In fact, even the permanent recipient type selectors are pretty noisy (over-salient) considering that users will typically use them maximally once per each recipient, and after changing the type, the dropdown then becomes irrelevant. There's absolutely no point of permanently having multiple dropdown markers for each recipient on screen. This is 2019 and ux-minimalism has long been part of best practice on any type of application or online presentation. Users know (not least from their Android phones) that they have to touch (tap/hover/focus) any element on the screen first in order to get at contextual actions, and that non-contextual/inapplicable actions are typically hidden to avoid clutter. PROPOSAL So I suggest to radically simplify/de-clutter both the recipient type selectors and the delete buttons by making them contextual, i.e. showing them only and exactly when they are needed. Ironically, this actually makes both of them MORE discoverable. 1) show recipient type selector and delete button only when applicable - when editing a recipient (this is a great way of assisting ux-discovery) - when hovering / focusing any part of a recipient row (name/type/delete) 2) hide all recipient type selector stylings (dropdown arrow, border box) and delete button when they are not applicable (i.e. when recipient is neither being edited nor hovered nor focused).
Here's my new proposal (Screenshot 1 out of 3). Jörg and reporter are right, recpient delete button shouldn't appear out of nowhere from underneath when clicking recipient type selector, which is undiscoverable, unexpected, and error-prone. As discussed in bug 1100103, we also don't want to clutter the entire recipient area with dozens of permanent delete buttons. In fact, even the permanent recipient type selectors are pretty noisy (over-salient) considering that users will typically use them maximally once per each recipient, and after changing the type, the dropdown then becomes irrelevant. There's absolutely no point of permanently having multiple dropdown markers for each recipient on screen. This is 2019 and ux-minimalism has long been part of best practice on any type of application or online presentation. Users know (not least from their Android phones) that they have to touch (tap/hover/focus) any element on the screen first in order to get at contextual actions, and that non-contextual/inapplicable actions are typically hidden to avoid clutter. PROPOSAL So I suggest to radically simplify/de-clutter both the recipient type selectors and the delete buttons by making them contextual, i.e. showing them only and exactly when they are needed. Ironically, this actually makes both of them MORE discoverable. 1) show recipient type selector and delete button only when applicable - when editing a recipient (this is a great way of assisting ux-discovery) - when hovering / focusing any part of a recipient row (name/type/delete) 2) hide all recipient type selector stylings (dropdown arrow, border box) and delete button when they are not applicable (i.e. when recipient is neither being edited nor hovered nor focused).