Bugzilla

I'll present a new proposal in my next comment.

I think we can't just ignore the UX problem pointed out by reporter of this bug and duplicates. They click on recipient type selector dropdown arrow (surely a legitimate click target!) and suddenly find their recipient deleted. Jörg's comment 30 actually confirms that problem: he doesn't want to end up deleting when clicking on the right side of recipient selector, which is same scenario as reporter's.

ux-error-prevention: users should not end up deleting recipients when they only want to change the recipient type

ux-discovery: our delete button isn't very easy nor intuitive to discover, as it only appears when hovering recipient type selector (which has no obvious logical relation to deleting recipient). Certain users might never change or touch the recipient type selector but they might still want to delete recipients efficiently.

I've adjusted the summary to describe the problem without favoring one specific solution.

I'll present a new proposal in my next comment.

I think we can't just ignore the UX problem pointed out by reporter of this bug and duplicates. They click on recipient type selector dropdown arrow (surely a legitimate click target!) and suddenly find their recipient deleted. Jörg's comment 30 actually confirms that problem: he doesn't want to end up deleting when clicking on the right side of recipient selector, which is same scenario as reporter's.

- ux-error-prevention: users should not end up deleting recipients when they only want to change the recipient type

- ux-discovery: our delete button isn't very easy nor intuitive to discover, as it only appears when hovering recipient type selector (which has no obvious logical relation to deleting recipient). Certain users might never change or touch the recipient type selector but they might still want to delete recipients efficiently.

I've adjusted the summary to describe the problem without favoring one specific solution.