Part 3 is a peripheral mini bug fix for the recipient type selector. STR 1) composition, add 5 recipients (sic) R1, R2 etc. 2) focus recipient type menulist of R1 (click menulist or shift-tab from R1) 3) use addressing widget scrollbar to scroll down to the last recipient (R5). 4) press "C" because you think you're in msg body and want to write "Conny"; or press cursor down (again assuming maybe you're navigating msg body) Actual result - user has unintentionally changed recipient type, but the focused menulist where the change occured is still hidden; that's error-prone (and can be pretty consequential, imagine unintentionally changing bcc to cc) Expected result - when pressing keys on a focused element (which may change its value), the visibility of that element must be ensured to avoid user errors (unintentional change of value) - here: any potentially value-changing keypress on the menulist should scroll it back into view. (Ideally, unrelated keypresses like alt+s to focus subject should be ignored).
Bug 1528840 Comment 43 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Part 3 is a peripheral mini bug fix for the recipient type selector. STR 1) composition, add 5 recipients (sic) R1, R2 etc. 2) focus recipient type menulist of R1 (click menulist or shift-tab from R1) 3) use addressing widget scrollbar to scroll down to the last recipient (R5). 4) press "C" because you think you're in msg body and want to write "Conny"; or press cursor down (e.g. with an intention of navigating recipients list with cursor keys after we've enabled that in bug 1527547) Actual result - user has unintentionally changed recipient type, but the focused menulist where the change occured is still hidden; that's error-prone (and can be pretty consequential, imagine unintentionally changing bcc to cc) Expected result - when pressing keys on a focused element (which may change its value), the visibility of that element must be ensured to avoid user errors (unintentional change of value) - here: any potentially value-changing keypress on the menulist should scroll it back into view. (Ideally, unrelated keypresses like alt+s to focus subject should be ignored).