Closed
Bug 741517
Opened 13 years ago
Closed 12 years ago
Default PDF Viewer Selector
Categories
(Firefox :: PDF Viewer, defect)
Tracking
()
People
(Reporter: bdahl, Assigned: bdahl)
References
Details
(Whiteboard: [pdfjs-c-ff-integration])
On first run check for all other pdf mime type listeners and offer a list for the user to choose which viewer they want to be their default viewer.
Comment 1•13 years ago
|
||
Without something like this any user that already has a pdf plugin installed (I'm guessing the majority of our users) won't see the benefits of pdf.js.
tracking-firefox14:
--- → ?
Comment 2•13 years ago
|
||
In https://bugzilla.mozilla.org/show_bug.cgi?id=739043#c2, Dao suggests that leaving the user with Adobe's PDF reader would leave them vulnerable to security issues. We'll probably discuss the current state of PDF.JS w/r/t FF14 at tomorrow's channel meeting.
Updated•13 years ago
|
tracking-firefox14:
+ → ---
tracking-firefox15:
--- → +
Comment 3•13 years ago
|
||
Given bug 773397, tracking for FF16's release but not FF15.
tracking-firefox16:
--- → +
Comment 5•12 years ago
|
||
Brendan, it's been a couple of weeks with no activity on this bug. This is still on our radar for 16 so I'm assigning to you to determine who will be working on this bug and preparing a fix for uplift to Aurora.
Assignee: nobody → bdahl
Updated•12 years ago
|
Updated•12 years ago
|
Whiteboard: [pdfjs-c-ff-integration]
Comment 7•12 years ago
|
||
(In reply to Dave Townsend (:Mossop) from comment #6)
> Why did this get untracked from the release?
Possibly because native PDF is not shipping in 16.
Updated•12 years ago
|
Comment 8•12 years ago
|
||
Currently with a new profile, in Firefox 18 (first version shipped with PDF Viewer) the default PDF viewer is the plugin of the default PDF reader and in Firefox 20 it's PDF Viewer.
In addition, with a profile that sets a PDF plugin as PDF viewer in Firefox 20, PDF Viewer is declared as the PDF viewer in the options but the PDF plugin is still used. That is an issue.
When updating to Firefox 18, a prompt should be presented to the user in order to choose its new PDF viewer.
tracking-firefox18:
--- → ?
Comment 9•12 years ago
|
||
The new PDF viewer will be shipping with FF19, so tracking for that release.
Brendan - can you look into
(In reply to Scoobidiver from comment #8)
> In addition, with a profile that sets a PDF plugin as PDF viewer in Firefox
> 20, PDF Viewer is declared as the PDF viewer in the options but the PDF
> plugin is still used. That is an issue.
Comment 10•12 years ago
|
||
(In reply to Alex Keybl [:akeybl] from comment #9)
> The new PDF viewer will be shipping with FF19
You should file a bug to disable it in FF 18 because Preview in Firefox is available in the drop-down menu of PDF Document in Options - Applications.
Comment 11•12 years ago
|
||
(In reply to Scoobidiver from comment #10)
> (In reply to Alex Keybl [:akeybl] from comment #9)
> > The new PDF viewer will be shipping with FF19
> You should file a bug to disable it in FF 18 because Preview in Firefox is
> available in the drop-down menu of PDF Document in Options - Applications.
Brendan let me know he's filing/landing today.
Comment 12•12 years ago
|
||
Can we get a status update here? Bug number for comment 11?
Flags: needinfo?(bdahl)
Comment 13•12 years ago
|
||
Assignee | ||
Comment 14•12 years ago
|
||
I'm still trying to find the meeting notes, but awhile ago it was decided(with input from Asa I believe) that it was okay for pdf.js to become the default reader and not prompt since it is easy to disable in the options menu.
(In reply to Scoobidiver from comment #8)
> In addition, with a profile that sets a PDF plugin as PDF viewer in Firefox
> 20, PDF Viewer is declared as the PDF viewer in the options but the PDF
> plugin is still used. That is an issue.
I cannot reproduce this, but if you have steps please open another bug to report this issue.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(bdahl)
Resolution: --- → WONTFIX
Updated•12 years ago
|
status-firefox19:
--- → wontfix
status-firefox20:
--- → wontfix
You need to log in
before you can comment on or make changes to this bug.
Description
•