Show PDF inline
|Show PDF inline|
|Release target||Firefox 18|
|Status note||Landed in Firefox 14 nightly but didn't make the uplift. Targeting Firefox 15 or 16.|
|Product manager||Asa Dotzler|
|Directly Responsible Individual||Alex Limi|
|Lead engineer||Bill Walker|
|QA lead||Mihaela Velimiroviciu|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
The current handling of PDFs in Firefox isn't great. The plugin-based renderer on Windows has several issues, and the situation on the Mac is that there really isn't a good renderer available for PDFs.
We want to be able to show PDFs inline in the browser on at least the majority of the platforms we support, and be able to wrap our own UI around it to support things like viewing and saving to disk, etc.
Goal: Make viewing of PDF in the web browser as painless as possible.
2. Users & use cases
- Ability to view a PDF document inline on Windows, Mac OS X, and possibly Linux.
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
Use the PDF.js renderer
Alternatives that were considered, but decided against:
- Use the platform support for PDF in the cases where it's available, e.g. on Mac OS X via PDFkit: http://code.google.com/p/firefox-mac-pdf/
- We could also do a hybrid approach, e.g. use Adobe plugin on Windows, and PDFkit on the Mac.
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
Landed in m-c during Firefox 14 cycle. Uplift criteria include
- getting past the add-on manager warnings (moving the add-on to a different directory, according to Mossop)
|Theme / Goal||Experience|
|Secondary roadmap||Firefox Desktop|
Team status notes
|Products||`||Sorting out remaining requirements. Add-on blocked, Printing, Finding, and select, copy, paste discussed at last meeting.|
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
|Quality assurance||in progress||Test plan|
|755957||SecReview: Show PDF inline||P4||NEW|
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);" contains strip markers and therefore it cannot be parsed sufficiently.