Show PDF inline

Please use "Edit with form" above to edit this page.

Status

Show PDF inline
Stage	Definition
Status	`
Release target	`
Health	At risk
Status note	Need to figure out platform approach.

{{#set:Feature name=Show PDF inline

|Feature stage=Definition |Feature status=` |Feature version=` |Feature health=At risk |Feature status note=Need to figure out platform approach. }}

Team

Product manager	`
Directly Responsible Individual	Alex LImi
Lead engineer	Josh Aas?
Security lead	`
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	Mihaela Velimiroviciu
UX lead	`
Product marketing lead	`
Operations lead	`
Additional members	`

{{#set:Feature product manager=`

|Feature feature manager=Alex LImi |Feature lead engineer=Josh Aas? |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Mihaela Velimiroviciu |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

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

`

3. Dependencies

`

4. Requirements

• Ability to view a PDF document inline on Windows, Mac OS X, and possibly Linux.

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

• The download manager article talks about how to show content inline and allow people to download it too: http://limi.net/articles/improving-download-behaviors-web-browsers

Stage 3: Planning

7. Implementation plan

• Figure out what our approach is going to be.

Alternatives:

1. 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/
2. We could also do a hybrid approach, e.g. use Adobe plugin on Windows, and PDFkit on the Mac.
3. Use the PDF.js renderer

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |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. |Feature users and use cases=` |Feature dependencies=` |Feature requirements=* Ability to view a PDF document inline on Windows, Mac OS X, and possibly Linux. |Feature non-goals=` |Feature functional spec=` |Feature ux design=* The download manager article talks about how to show content inline and allow people to download it too: http://limi.net/articles/improving-download-behaviors-web-browsers |Feature implementation plan=* Figure out what our approach is going to be.

Alternatives:

1. 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/
2. We could also do a hybrid approach, e.g. use Adobe plugin on Windows, and PDFkit on the Mac.
3. Use the PDF.js renderer

|Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority	P2
Rank	999
Theme / Goal	`
Roadmap	User Experience
Secondary roadmap	`
Feature list	Platform
Project	`
Engineering team	Platform

{{#set:Feature priority=P2

|Feature rank=999 |Feature theme=` |Feature roadmap=User Experience |Feature secondary roadmap=` |Feature list=Platform |Feature project=` |Feature engineering team=Platform }}

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	`
Product marketing	`	`
Operations	`	`

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}