UCID: Email-142 User Story: As a user, I want to see the total size of files attached to an email to make it easier to determine how much data will be required to send the email.
Summary: [B2G][E-Mail][User Story] Attachments total file size → [E-Mail][User Story] Attachments total file size
I am planning to work this for the current v1.1 "sprint" but have not started yet. I'll mark this bug as 'assigned' once I do; people should feel free to snipe this one.
Assignee: nobody → bugmail
Whiteboard: [sprint: 2013/02/15]
(turns out this is P2 and not leo+)
Assignee: bugmail → nobody
Whiteboard: [sprint: 2013/02/15]
Total file size is shown in the draft email attachment spec - https://bug838006.bugzilla.mozilla.org/attachment.cgi?id=710545
Whiteboard: u=user c=email s=v1.1-sprint-1 → u=user c=email s=v1.1-sprint-2
Whiteboard: u=user c=email s=v1.1-sprint-2 → email@example.com c=email s=v1.1-sprint-2
Whiteboard: firstname.lastname@example.org c=email s=v1.1-sprint-2 → email@example.com c=email s=v1.1-sprint-2 [LOE:L]
Whiteboard: firstname.lastname@example.org c=email s=v1.1-sprint-2 [LOE:L] → [LOE:L]
I think LOE:L may be a high estimate since the attachment objects currently already surface a sizeEstimateInBytes attribute. So this is just a question of having the UI tally those counts and display an aggregate number.
Andrew, I was asked to give the LOE tags on every bugs that related to leo+, and I was not sure the implementation of calculating the size of attachments in email, so I gave LOE:L first. Sounds like it's not complex and just waiting for the UI, so feel free to change it since you know this better than me, thanks.
Clearing tracking-b2g18 flag from User Story bugs. This flag is for bugs that we would take fixes for in the 1.x branch. Feature work should be officially slotted into a release instead with leo+. If this story is intended for v1.1, please nominate for leo? blocking.
tracking-b2g18: + → ---
The latest email attachment flows, showing total file size, have been moved to Dropbox: https://www.dropbox.com/s/5giljes7ao9gyrg/email-attachments.pdf The display of the size units is TBD, but if anyone has an existing reference, feel free to forward it to me. Thanks!
I think it's great that we can have attachments! Pretty exciting stuff. I was wondering about the flow... do you have to click on the attachment section again to add another picture, attachment, etc? Or is there going to be a way to do a multiple attachment of pictures/contacts/etc? without having to go back to the email? I really like the total size idea as well as the progress bars for downloading the attachments.
(In reply to Naoki Hirata :nhirata from comment #8) > I was wondering about the flow... do you have to click on the attachment > section again to add another picture, attachment, etc? Or is there going to > be a way to do a multiple attachment of pictures/contacts/etc? without > having to go back to the email? Thanks, Naoki... For now the idea is you can only select one file at a time. So, if a user wants to have multiple attachments, they would have to tap on the plus button from inside of the email compose screen and repeat the attachment flow a second time.
https://moztrap.mozilla.org/manage/case/6921/ created. A couple of visual bugs in terms of alignment filed.
More test cases will come later with other attachment type implementations.
Reposting link to spec in dropbox as it appears to have been broken... https://www.dropbox.com/s/c9rrz0ymxvg0osw/email-attachments.pdf
blocking-b2g: --- → leo?
needed to be +'d for 1.1 work since its a feature/user story
-- Mass Edit -- These user stories are not P1, therefore not blockers to shipping. We will track for now and look into how to keep tabs on these going forward.
blocking-b2g: leo? → -
status-b2g18: --- → affected
tracking-b2g18: --- → +
This was implemented for v1.1 as part of bug 838006.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
status-b2g18: affected → fixed
status-b2g18-v1.0.1: --- → wontfix
Depends on: 838006
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.