STR 1) compose, have several accounts/identities with different combinations of Auto-CC/BCC 2) click From selector, navigate identity list with cursor up/down 3) navigate to "Customize From Address" (without pressing Enter) **Actual** - 2) each identity which you navigate is immediately applied to the compose window, you can see Auto-CC/BCC entries changing. - not helpful as those fields are covered by the dropdown - potentially datalossy because we're doing all sorts of things to existing recipients as we swap Auto-CC/BCC from one identity to another. I have recently tamed that to be less greedy in Bug 1623285, but I wouldn't bet on it. - 3) it's unexpected that just navigating onto the last option immediately pops up the alert - bad for blind users, too. Maybe they just wanted to let their screenreader 'read' that last option, as opposed to choosing it. **Expected** - list navigation should do just that: navigate the list. As long as I haven't pressed Enter on an option, it should not be applied. I don't think this is a case of live preview as for font and style selectors. Plus the inherent recipient dataloss risk from our Auto-CC/BCC algorithms should be avoided. - 'Customize From Address' should not suddenly jumping into into users face when he didn't explicitly confirm that with Enter yet (important for the blind)
Bug 1635124 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
STR 1) compose, have several accounts/identities with different combinations of Auto-CC/BCC 2) click From selector, navigate identity list with cursor up/down 3) navigate to "Customize From Address" (without pressing Enter) **Actual** - 2) each identity which you navigate is immediately applied to the compose window, you can see Auto-CC/BCC entries changing. - not helpful as those fields are covered by the dropdown - potentially datalossy because we're doing all sorts of things to existing recipients as we swap Auto-CC/BCC from one identity to another. I have recently tamed that to be less greedy in Bug 1623285, but I wouldn't bet on it. - 3) it's unexpected that just navigating onto the last option immediately pops up the modal alert - bad for blind users, too. Maybe they just wanted to let their screenreader 'read' that last option, as opposed to choosing it. **Expected** - list navigation should do just that: navigate the list. As long as I haven't pressed Enter on an option, it should not be applied. I don't think this is a case of live preview as for font and style selectors. Plus the inherent recipient dataloss risk from our Auto-CC/BCC algorithms should be avoided. - 'Customize From Address' modal dialog should not suddenly jumping into into users face when he didn't explicitly confirm that with Enter yet (important for the blind)
STR 1) compose, have several accounts/identities with different combinations of Auto-CC/BCC 2) click From selector, navigate identity list with cursor up/down 3) navigate to "Customize From Address" (without pressing Enter) **Actual** - 2) each identity which you navigate is immediately applied to the compose window, you can see Auto-CC/BCC entries and Recipient buttons changing. - not helpful as those fields are covered by the dropdown - potentially datalossy because we're doing all sorts of things to existing recipients as we swap Auto-CC/BCC from one identity to another. I have recently tamed that to be less greedy in Bug 1623285, but I wouldn't bet on it. - 3) it's unexpected that just navigating onto the last option immediately pops up the modal alert - bad for blind users, too. Maybe they just wanted to let their screenreader 'read' that last option, as opposed to choosing it. **Expected** - list navigation should do just that: navigate the list. As long as I haven't pressed Enter on an option, it should not be applied. I don't think this is a case of live preview as for font and style selectors. Plus the inherent recipient dataloss risk from our Auto-CC/BCC algorithms should be avoided. - 'Customize From Address' modal dialog should not suddenly jumping into into users face when he didn't explicitly confirm that with Enter yet (important for the blind)