As a user I want to CC/BCC to be collapsed into a single line so I have more space in the message body space to type my email. The acceptance criteria will be defined by the UX design.
In the compose email view, the cc, bcc and attachments fields take up so much vertical space that the user has to scroll to start typing in the message body field. This adds an unnecessary and very annoying step for every new email. In the spec, the cc/bcc and attachments fields are merged into a single, expandable field to preserve the vertical space and allow the user to tap directly on the message body field without scrolling. The interaction pattern is available on page 5 of the email attachment spec, located here: https://www.dropbox.com/s/5giljes7ao9gyrg/email-attachments.pdf STR: 1) Launch email app 2) Tap new email icon 3) In compose view, enter a contact 4) To enter text you must first scroll, then tap. Desired behaviour: cc/bcc and attachments are combined into a single field that, when tapped, expands to show all three fields (see page 5 of the spec).
Flagging Peter on needinfo? to ensure this gets slotted for a 1.2 sprint. I realized this earlier work addresses Productivity18 in the product backlog spreadsheet (where I've also added the bug number).
Thanks for adding the bug number Stephany. It's prioritized in the right spot on the backlog, so we'll see if it ends up in 1.2.
Created attachment 8414230 [details] [Email]Expand_Collapse cc_bcc list.pdf Spec uploaded. Since we have another users story talks about expand/collapse attachments, how about change this bug title to " [email] cc/bcc fields in compose view do not collapse / expand" ?
(In reply to Juwei Huang from comment #3) > Since we have another users story talks about expand/collapse attachments, > how about change this bug title to " [email] cc/bcc fields in compose view > do not collapse / expand" ? Sure! Changed. At least for email, please feel free to change the subject if you think it's wrong/misleading, etc. In the case where I or others have added some low-level implementation details to the subject, it's preferable if you can leave them in there, but feel free to re-phrase or add-in the UI/UX-facing implications/etc and push the implementation details to the end. If you lack the ability to change the subject (via the "edit" link that will be around it), please make sure that you've explicitly listed your "Bugzilla Email" at https://phonebook.mozilla.org/edit.php since I think that automatically grants you the required bugzilla privileges. I don't see one there right now, but since it's the same as your mozilla.com email I don't know if it's automagic or what.
Since the scope reduction per comment 3 has made this just about the cc/bcc collapse/uncollapse and Sri has filed a bug on just that and not much has happened on this bug, duping to the newer bug with the reduced scope.