Platform/Layout/Printing and fragmentation: Difference between revisions
(Update bugzilla query) |
No edit summary |
||
| Line 25: | Line 25: | ||
<bugzilla> | <bugzilla> | ||
{ | { | ||
"component": ["Print Preview", "Printing: Output", "Printing: Setup", "Printing"], | "component": ["Print Preview", "Printing: Output", "Printing: Setup", "Printing", "PDF Viewer"], | ||
"whiteboard": "[frag2020]" | "whiteboard": "[frag2020]" | ||
} | } | ||
| Line 34: | Line 34: | ||
<bugzilla> | <bugzilla> | ||
{ | { | ||
"component": ["Print Preview", "Printing: Output", "Printing: Setup", "Printing"], | "component": ["Print Preview", "Printing: Output", "Printing: Setup", "Printing", "PDF Viewer"], | ||
"whiteboard": "[print2020]" | "whiteboard": "[print2020]" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
Revision as of 21:32, 2 March 2020
This page provides information about our efforts in 2020 to improve the platform parts of printing and fragmentation in Firefox. Given how closely linked the frondend and platform parts of printing are, this will inevitably involve some frontend work too.
Rationale
Support for printing in Firefox has historically been poorly maintained, and is currently in a dismal state compared to other browsers. There are two main areas for improvement:
- Printing UX: Firefox’s printing UI/UX lacks consistency and is complicated and confusing compared to the competition. Print settings are displayed differently across operating systems, different methods of accessing printing lead to different dialogs, and print preview is not displayed by default on macOS.
- Printing output: There is a significantly-sized backlog of user-reported bugs related to print output (for both printing devices and PDF export). Some of these bugs include cases where printing fails completely, several pages are missing, or the printed layout is just incorrect.
OSX is a popular platform among web developers and designers. It is important we provide a means for testing web content accessibility in OSX. Historically, our OSX support has been plagued with performance issues, but we can still provide a good benchmark for developers to test with. After we reach API completeness, we will do a second pass to optimize the experience for VoiceOver users and assure the performance is optimal and comparable to other browsers.
Milestone One (2020 H1)
Fragmentation
To be pulled from "Milestone Next" below.
Printing
To be pulled from "Milestone Next" below.
Milestone Next (2020 H2+)
Fragmentation
19 Total; 10 Open (52.63%); 9 Resolved (47.37%); 0 Verified (0%);
Printing
177 Total; 117 Open (66.1%); 53 Resolved (29.94%); 7 Verified (3.95%);