Open
Bug 1679515
Opened 3 years ago
Updated 3 years ago
Low Ink/toner levels notification should be displayed on the new modal as well
Categories
(Toolkit :: Printing, enhancement, P3)
Tracking
()
NEW
People
(Reporter: vlucaci, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [print2020] [old-ui-] )
Attachments
(1 file)
5.86 KB,
image/png
|
Details |
Affected versions
- 85.0a1
- 84.0b5
Affected platforms
- Windows 10x64
- macOS 10.15.7
- Ubuntu 20.04
Prerequisites
- Have low toner/ink levels on the printer in use.
Steps to reproduce
- Launch FF
- Go to any random webpage.
- CTRL+P.
Expected result/Enhancement Suggestion
- As per system modal, a Status field is displayed, stating that the printer in use is low on ink/toner.
Actual result
- No information is displayed in the new modal in regards to the ink levels on the printer.
Suggested Severity
- S4 since the user is notified via old modal and on Windows 10 by a system pop-up notification.
Additional notes
- This addition would greatly improve on the quality of the UX , since the user will know before committing to a lengthy(or any for that matter) print job that his ink/toner levels are low.
Reporter | ||
Comment 1•3 years ago
|
||
Hello,
As per mentioned above in the additional notes section, this would greatly improve the UX as per seen in attachment provided below from macOS 10.15.7 system modal.
https://drive.google.com/file/d/15Qv-bCS8dGD6-FRR7U4-g8KoDq4_JLx9/view?usp=sharing
The user would very much benefit from this, especially if using color cartridges which are expensive
Comment 2•3 years ago
|
||
Sending this over to frontend since this is their decision to make, not the Platform team's.
Component: Print Preview → Printing
Product: Core → Toolkit
Updated•3 years ago
|
Whiteboard: [print2020_v85] [old-ui-] → [print2020_v87] [old-ui-]
Updated•3 years ago
|
Severity: -- → S4
Priority: -- → P3
Whiteboard: [print2020_v87] [old-ui-] → [print2020_v88] [old-ui-]
Updated•3 years ago
|
Whiteboard: [print2020_v88] [old-ui-] → [print2020] [old-ui-]
You need to log in
before you can comment on or make changes to this bug.
Description
•