Closed Bug 747073 Opened 12 years ago Closed 8 years ago

Adobe Reader (10.1.3) doesn't work with Firefox (OSX) in default (64-bit) mode

Categories

(Plugins Graveyard :: PDF (Adobe), defect)

Product:
Plugins Graveyard
Component:
PDF (Adobe)
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: cww, Assigned: smichaud)

References

Details

(Keywords: qawanted) 

From https://support.mozilla.org/en-US/questions/925055

If you have the Acrobat NPAPI plugin and the latest version of Reader (or maybe Acrobat), you don't have in-browser PDF capabilities and you're not prompted for downloading the PDF.

The update happened around 4/10.
Adding qawanted and pinging in #qa to get some eyes on this bug in preparation for outreach to Adobe, since we have a strong suspicion this is correlated to their most recent reader release:

"This issue appears only using the combination MacOS X, Firefox 11 with the Adobe Acrobat (Update 10.1.3) Viewer Plugin."
Keywords: qawanted
Apparently, the update is setting the Preferences > Applications for pdfs to use the NPAPI plugin (which doesn't work) rather than use Adobe Acrobat
Acrobat NPAPI plugin is only working if you are using FireFox in 32 bit. FF 64 bit is not supported yet. You have to set back in FF Preferences > Applications the Adobe Acrobat in order to open the PDF in Acrobat if you are using FF 64 bit
Do we know why the recent update changed this setting for a lot of users?
We are registered for PDF mimetype as an NPAPI plugin. There is no way we can tell the FF Browser on the plugin side that we don't want to be loaded. This is a request we have done and that have been dropped:https://wiki.mozilla.org/NPAPI:PluginOptOut
However, could you confirm that you are running FF 64 bit. You should be able to see your PDF in 32 bit in the Browser
For all recent versions of Firefox and recent versions of OSX, Firefox runs in 64-bit. The problem affecting thousands of users that the default case is that they can't download or view PDFs.
Steven - can you figure out exactly what is going on here and recommend a course of action?
Assignee: nobody → smichaud
See Also: → 746254, 746713
In 64-bit mode, the Adobe Reader plugin loads but doesn't do anything.

In 32-bit mode:  The Adobe Reader plugin crashes loading any PDF file on FF 12 nightlies and up (bug 746713).  In FF 12 betas and below it works (sort of), but causes a high-volume crash in Reader code (bug 746254).

These are all Adobe bugs.
We should blocklist this plugin. Breaking PDF download/display for the vast majority of our users is unacceptable.

Who can get us started with blocking it for 64-bit Mac OS X?
(Following up comment #8)

> In 64-bit mode, the Adobe Reader plugin loads but doesn't do anything.
>
> In 32-bit mode: The Adobe Reader plugin crashes loading any PDF file
> on FF 12 nightlies and up (bug 746713).  In FF 12 betas and below it
> works (sort of), but causes a high-volume crash in Reader code (bug
> 746254).
>
> These are all Adobe bugs.

I need to update the second paragraph:

In 32-bit mode:  The Adobe Reader plugin crashes loading any PDF file
in non-release FF distros (nightlies on	all branches except the	beta
branch, bug 746713).  In FF releases (currently FF 12 and below) it
works (sort of), but causes a high-volume crash in Reader code (bug
746254).
(In reply to comment #11)

I tend to agree with Josh.  Sorry, Rudi, but the current version of the Adobe Reader plugin for OS X is just too buggy.

Alex and Kev, do you agree?

If so, I imagine it's one of you that'll need to start the blocklisting process.
By the way, if we're not going to blocklist the plugin entirely, it does make sense to blocklist it only in 64-bit mode (as Josh suggests).  It doesn't crash in 64-bit mode, but it also has no functionality (it doesn't work at all).
(Following up comment #12)

Argh, I	got the	bug numbers reversed.  So I need to update the second
paragraph again:

In 32-bit mode:  The Adobe Reader plugin crashes loading any PDF file
in non-release FF distros (nightlies on all branches except the beta
branch, bug 746254).  In FF releases (currently FF 12 and below) it
works (sort of), but causes a high-volume crash in Reader code (bug
746713).
Blocks: 750387
(In reply to Steven Michaud from comment #13)
> I tend to agree with Josh.  Sorry, Rudi, but the current version of the
> Adobe Reader plugin for OS X is just too buggy.
> 
> Alex and Kev, do you agree?

Yep, I've filed bug 750387. We'll evaluate the user experience of the blocklist addition prior to rolling this out to production.
Summary: Adobe Reader (10.1.3) doesn't work with Firefox 11 (OSX) → Adobe Reader (10.1.3) doesn't work with Firefox (OSX) in default (64-bit) mode
Meanwhile Adobe Reader had been updated to 10.1.4 (in 8/2012 ?), but it still
isn't able to display inline PDF files in a firefox running 64-bit.

A manual reinstall of the latest Adobe Reader XI (11.0.0) didn't help, either.
I am done with this bug, no longer an issue for me.

BTW, latest beta crashed on me, am back to 16.0.2, no issues at present. 

So, please drop me for now from bugzilla, if you will.
(In reply to comment #18)

See bug 811085.  I'm able to get Adobe Reader 10.1.4 to work for me in at least some cases.

(According to Adobe Reader XI's installer, it only works with Safari.)
This has been a long standing bug. What is the current status as of Firefox 20.0a1 Nightly and the latest Adobe Reader plugin?
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #21)

Well, the latest Adobe XI (11.0) plugin just opens a dialog box telling me
that it is unsupported on the 64-bit mac platform.

Fortunately, Firefox 20.0a1 Nightly has the built in JS PDF Viewer enabled
by default on the Mac (pdfjs.disabled = false).
Re:  --- Comment #22 from jrgn.keil@gmail.com 2013-01-05 07:55:49 PST ---
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #21)

> Well, the latest Adobe XI (11.0) plugin just opens a dialog box t> elling me
> that it is unsupported on the 64-bit mac platform.
>
> Fortunately, Firefox 20.0a1 Nightly has the built in JS PDF Viewer enabled
> by default on the M

MY EEPLY!!!/ QUESTION???
No idea what you are talking about, this problem is long since solved.  Now running Mozilla Firefox version 17.0.1, Adobe Reader 10.1.4, with a few plugins loaded, most not.
There is no trouble any longer downloading PDFs, option box comes on, asking me to open PDF or not (have not memorized exact wording), I clik "Yes" and PDF opens.  This puts PDF into Download folder, but I prefer renaming and saving into specialied folder.  Can delete from Download at a later time.

Also can use Safari, which works more like you wish Firefox would:  There is a built-in PDF reader, which has its own way of allowing downlosd and saving under new name.  

SO, RELAX, GUYS!!!
(In reply to skeptiker from comment #23)

Please read the bug's description, it is about the in-browser PDF capabilities,
that is, displaying a PDF document inline in the Firefox web browser page, using
Adobe Reader plugin, on the MacOS X 64-bit binary.

Sure, there are several workarounds for reading PDF documents with 
64-bit Firefox on MacOS.  But you won't get inline PDF display using
Adobe's plugin in 64-bit Firefox on MacOS.
Can I correct you slightly?  When I attach a PDF to my email in Google's gmail, then I can later open it INSIDE MOZILLA FIREFOX and read it. I don't have to export it first, but is is INLINE, which you seem to say is impossible.
No.

A quick check with Google gmail indicates that Google renders the PDF Document
on the server and sends a PNG image per page to the browser.  So it actually
displays inline PNG images, and not PDF files!

Your example is not relevant for this bug.
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.