Closed Bug 1155419 Opened 10 years ago Closed 7 years ago

Should warn end users about adding too large of an attachment

Categories

(Firefox OS Graveyard :: Gaia::Bugzilla Lite, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: nhirata, Unassigned)

References

Details

(Whiteboard: [spark])

1. install bugzilla lite staging client : via https://bzlite-staging.herokuapp.com/install.html 2. log into bugzilla 3. add a bunch of mp3 attachments. Expected: some sort of warning stating you're about to send a large number of data... Actual: no warning
Whiteboard: [ingite]
Whiteboard: [ingite] → [ignite]
Priority: -- → P2
Whiteboard: [ignite] → [spark]
We show the size of the files in the UI when submitting a bug, the user has to specifically attach them. I dont think we need extra warning here.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Sorry, we do need the warning if there's going to be issues with file size uploaded to bugzilla.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
bug 1155420 shows that even though the size is placed in the attachments, without a warning the end user would expect the file to be uploaded to bugzilla.
As far as I know, there is a parameter in Bugzilla called 'maxattachmentsize' (default = 1000 Kb) that controls the maximum allowable attachment size. Attachments larger than either the 'max_allowed_packet' or 'maxattachmentsize' value will not be accepted by Bugzilla. Hi Jacqueline, What is your opinion? Thank you!
Flags: needinfo?(jsavory)
For this case we just need a dialogue message that informs the user the attachment is too big. We can use: Title: Attachment is too large Body: The selected file exceeds the <limit amount> size limit and cannot be attached. Button: Ok Let me know if this works, thanks!
Flags: needinfo?(jsavory)
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Closed: 10 years ago7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.