Open
Bug 1342770
Opened 8 years ago
Updated 2 years ago
Ambiguous "N files downloading" in downloads panel (is "other/more"; can be understood as "total)
Categories
(Firefox :: Downloads Panel, defect, P5)
Firefox
Downloads Panel
Tracking
()
NEW
People
(Reporter: aryx, Unassigned)
References
Details
(Whiteboard: [CHE-MVP])
Attachments
(1 file)
|
(deleted),
image/png
|
Details |
screenshot of issue (ignore that it's German)
Firefox Nightly 54.0a1 + 53.0a2, both latest version.
Bug 1269958 changed the label for the aggregation of downloads which aren't shown in the download panels if there are more than the view allows to "N files downloading". Before it was "N other downloads". If one downloads 10 or more files, the label becomes ambiguous because it can be understood as a summary of all downloads at the bottom but it shows the summary of all other downloads.
|
||
Comment 1•8 years ago
|
||
ni? UX designer to address.
Morpheus/Bryant, please comment on comment 0 ambiguity.
Flags: needinfo?(mochen)
Flags: needinfo?(bmao)
|
||
Comment 2•8 years ago
|
||
I agree. The summary label here did have the ambiguity issue as stated above. We will consider to bringing back the "+" or "others" in the label in the future version. I've already reported the issue to our copywriter Michelle for her suggestion.
Flags: needinfo?(mochen)
Flags: needinfo?(bmao)
|
|
||
Comment 3•8 years ago
|
||
Keep ni? on Bryant to track UX spec revision. Developer will then fix this bug based on revised UX spec.
Flags: needinfo?(bmao)
|
||
Updated•8 years ago
|
Whiteboard: [CHE-MVP]
|
|
||
Comment 4•8 years ago
|
||
Bryant, any update from copywriter or on UX spec revision?
|
||
Updated•8 years ago
|
Priority: -- → P3
|
|
||
Comment 5•7 years ago
|
||
Valid issue, but it doesn't seem there is anyone working on it or tracking it right now, demoting to P5 to reflect reality.
Flags: needinfo?(bmao)
Priority: P3 → P5
|
||
Comment 6•6 years ago
|
||
Could it maybe be changed to "N more files downloading"?
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•