View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022588 | mantisbt | attachments | public | 2017-03-27 02:41 | 2019-03-16 20:21 |
Reporter | icoams | Assigned To | cproensa | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 2.2.0 | ||||
Summary | 0022588: Oversize upload is now skipped with no Message prompted | ||||
Description | Attempted to upload file with size larger than maximum size upon both the "Report issue" and "Issue Detail - add note" UI. Both behaved the same and just skip the upload section with no message prompted. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
related to | 0021801 | closed | cproensa | File attachment GUI allows larger files than permitted |
related to | 0025464 | closed | cproensa | Enforce max-filesize in dropzone to alert and drop big files before form submission |
related to | 0003759 | confirmed | Duplicate bug is created when resubmitting after file upload failure |
Hi, any update? |
|
Unfortunately there are some nasty side-effects as well, see: 0021801 - it will sabotage e-mail notifications. |
|
Thanks for the reply. Is it possible to just make the error message always visible instead of only when the mouse is hovering over the oversized attachment? |
|
Hi, any update? |
|
I don't get the message. This seems to be caused by CSP violations. |
|
When I drop an oversized file to the 'Upload Files', there is no message telling me that the file is oversized unless I hover the mouse over the file. So unless user move the mouse over the oversized file, they have no way to know that the file is oversized:
|
|
@syncguru I didn't have a deeper look, but some of the known issues around file upload might be upstream bugs. |
|
Hi, any update? |
|
Hi, any update? |
|
Hi, any update? |
|
@icoams your weekly bumps are not going to help in getting this fixed. If this issue is important to you, I suggest you propose a pull request instead. |
|
Resolving this, as related to 0025464 |
|
:-) |
|