Last Comment Bug 825198 - Adobe Reader XI (Ver 11.0.0/11.0.01) will not open PDF files inline in Firefox
: Adobe Reader XI (Ver 11.0.0/11.0.01) will not open PDF files inline in Firefox
Status: NEW
:
Product: Core
Classification: Components
Component: Plug-ins (show other bugs)
: 17 Branch
: x86 Mac OS X
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on: 826002
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-28 04:41 PST by Tim Thompson
Modified: 2013-01-08 15:06 PST (History)
3 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Tim Thompson 2012-12-28 04:41:49 PST
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20100101 Firefox/17.0
Build ID: 20121128204232

Steps to reproduce:

When trying tp open Adobe documents using the reader the system hang and gives an error message to the effect that Adobe cannot open in this environment.  Ended up using Safari to view documents.


Actual results:

Nothing


Expected results:

Document should have opened as previously
Comment 1 Matthias Versen [:Matti] 2012-12-28 05:19:03 PST
This could be the same issue as bug 747073. Maybe we should update the block to include Version 11.
Open preferences/Applications and change PDF to be viewed by Acrobat(external) and not inside of Firefox.
Comment 2 Steven Michaud [:smichaud] (Retired) 2013-01-02 11:53:41 PST
Using the current (and so far only) version of Adobe Reader XI (11.0.0), I can't get it to load a PDF file "inline" (in a browser page) with either FF 17.0.1 or one of the FF 18 betas, on either OS X 10.6.8 or 10.7.5.  (I haven't yet tested on 10.8.2.)

It seems this is by design.  If I test with a fresh profile I get a dialog (in a separate window) telling me that "Adobe Reader cannot show documents in this browser", and telling me to "Please use your browser to download this file and open it in Adobe Reader."

Oddly, if I leave that dialog open a long time the plugin crashes.

But whether or not we can fix that problem, we aren't going to be able to get around Adobe's decision to stop supporting "inline" PDF files in Firefox.

By the way the Adobe Reader XI plugin is 64-bit only, so you might see a different error condition running in 32-bit mode.
Comment 3 Steven Michaud [:smichaud] (Retired) 2013-01-02 12:01:40 PST
> Maybe we should update the block to include Version 11.

Yes, that's probably the best solution.

If I disable the Adobe Reader XI plugin, I just get prompted to download the PDF file -- which is what we want, I think.

We'll need to test that the same thing happens when we block the plugin, though.
Comment 4 Steven Michaud [:smichaud] (Retired) 2013-01-02 12:26:46 PST
> Oddly, if I leave that dialog open a long time the plugin crashes.

Here's an example:

bp-7b608c1a-710d-4722-ae2c-101e22130102

I suspect we're seeing *lots* of these.

The report is extremely unhelpful -- the signature is "hang".  But the "hang" signature is currently the Mac topcrasher, and I wonder how many of those might be this crash/hang.

It'd help if we had an easy way to check how many of these "hang"s were associated with AdobePDFViewerNPAPI.plugin.  I'd bet that many of them are this bug.

Scoobidiver, can you think of a good way to check?
Comment 5 Matthias Versen [:Matti] 2013-01-02 13:03:28 PST
>Oddly, if I leave that dialog open a long time the plugin crashes.
I bet that the open dialog lets the plugin stop processing events.
The plugin gets killed after our hang detection (45s) kicks in and you have the same issue with other dialogs e.g. 817139 or on windows with the flash debug plugin that raises a dialog.
Comment 6 Steven Michaud [:smichaud] (Retired) 2013-01-02 13:05:38 PST
Yes, Matthias, you're probably right.
Comment 7 Steven Michaud [:smichaud] (Retired) 2013-01-02 14:11:50 PST
Here are some examples of embedded PDFs.  I mention them because they weren't easy to find.

http://acroeng.adobe.com/wp/?page_id=161
Comment 8 Steven Michaud [:smichaud] (Retired) 2013-01-08 14:39:41 PST
Adobe Reader XI v 11.0.1 was just released, but has the same problem.
Comment 9 Steven Michaud [:smichaud] (Retired) 2013-01-08 15:05:29 PST
> Adobe Reader XI v 11.0.1 was just released, but has the same problem.

Oops, I goofed on the version number.  It's actually "11.0.01".

Note You need to log in before you can comment on or make changes to this bug.