Reader plugin for Chrome versions 42+ no longer work

[Lisa Kensok]

As of 04/15/2015, Google has deprecated the NPAPI which the Adobe Reader plugin apparently uses (see NPAPI deprecation: developer guide - The Chromium Projects)   This means the Adobe Reader plugin for Chrome no longer works.

Does Adobe have any plans to provide a new plugin or extension for Chrome?

If not, what is an alternative that can handle .xdp forms?  I've tried PDF Viewer (PDF.js), Notable PDF, and Xodo but none of them handle .xdp files.

[abbyf10307956]

Same here - I updated Acrobat Reader and Regular Acrobat, and now the plugin now longer appears.  I need this in order to use QuickBooks online software to adjust printing - and this can only be done using the Acrobat plugin not the Chrome plugin.

Help!

[pwillener]

Since Chrome does/will no longer support NPAPI plugins, there is only one way: use a different browser.

[szgoyal]

Hi,

Please refer Help! Reader DC not working in Chrome,.

Thanks.

[tripster23 · Accepted solution]

All:  I use the Adobe Reader plugin a lot for work. I have found a workaround to the new Chrome version 42 update that has removed the NPAPI plugins, including Adobe Reader.

In the Chrome browser URL, type "chrome://flags". Find the flag called "Enable NPAPI Mac, Windows" and click "Enable".

Then, go back to your plugins in Chrome, "chrome://plugins". Make sure the Adobe Reader plugin is Enabled and the Chrome PDF Viewer is disabled. Everything should work as it did before.

[abbyf10307956]

Thank you, Tripster23!  I just tried this and it works.  I use QuickBooks Online and the program works best in Chrome.  Thank you so much for sharing this.

[Lisa Kensok]

Keep in mind that's a temporary fix.  According to Google's deprecation schedule (NPAPI deprecation: developer guide - The Chromium Projects) the NPAPI interface will be completely removed by September 2015.  After that, there won't be any enable flag.  Start looking for alternatives now.

I would prefer it if Adobe came up with a non-NPAPI alternative plugin -- I think Google is pushing for their PPAPI interface. Meanwhile, much as I dislike it, Internet Explorer still works with Adobe's plugin.  And I think Opera does too, but I don't want to have to tell my users to install Opera and learn one more browser.

[abbyf10307956]

Thanks P.Dow.  I'm not fond of IE either, but no way will I install a third browser. Sigh.

[Guest]

I'm seeing the same message re the Adobe plug-in's support ending on opera as of today. 😕

[SI_MSD7]

Just to update (in case anyone stumbles upon this thread)...Chrome no longer supports NPAPI plugins so viewing PDFs/PDF Forms within the Chrome browser (using the Adobe Reader plug-in) is no longer possible. It will default to Google native plug-in/pdf viewer.

More info on this topic can be viewed here:

Configure browser to use the Adobe PDF plug-in to open online PDF files

Change in support for Acrobat and Reader plug-ins in modern web browsers

[Richard25485149lhco]

This might have been answered elsewhere however I can't find it.

So it's 2022 and the NPAPI has been depricated, IE11 is dead (or in some final stages of).

The pdf plugin seems to be just well a 'skin' or 'link' to open the pdf in the standard application.

Is there any development in the plugin to move away from NPAPI and so that's its more than just a skin/link?

[Test Screen Name]

For many years Chrome has had a built in PDF viewer, made by Google. That's not going to change. Google specifically blocked Adobe from making a replacement.

[Richard25485149lhco]

Ok, well the replacement whilst good doesn't support XFA forms. So it feels like well adobe have just well said google chrome and edge have there own pdf viewer we just aren't going to develop anything. Adobe's plugin is basically a 'skin' / 'link' to have some buttons that look like their reader but require it to do a pdf that has other features that only the desktop program has and it's a no.

For many years Chrome has had a built in PDF viewer, made by Google. That's not going to change. Google specifically blocked Adobe from making a replacement.

By @Test Screen Name

I don't think that's true. Yes they stopped the NPAPI plugins but that was a security thing. 

There are still a few pdf readers around in the add on store. here is one.

https://chrome.google.com/webstore/detail/pdf-reader/ieepebpjnkhaiioojkepfniodjmjjihl

That has at least attempted the xfa problem with some success (ok it's based on pdf.js - but still)

and that's one person doing it in his free time.

https://github.com/Emano-Waldeck/pdf-reader/commits/master

So I presume that adobe could sit down and basically re-do their plugin - or perhaps contribute to the Chrome/Edge systems.

Meanwhile Chrome and Edge seem to be developing xfa abilities in their own way (with some success) - so it feels like whilst the rest of the world is activily trying to support a feature in Adobe PDFs, adobe are well stagnant in the pdf/browser/development.

Maybe I'm off the mark here but I'm just trying to tell you what I'm seeing and I can't see anything coming from Adobe in this field.

[Test Screen Name]

I think it's clear that end-user display of XFAs in a client isn't the least bit important to Adobe. If it was, they would have added XFA support to their mobile version. Adobe's strategy, such as it is, is components of AEM, which do live translation of XFA forms to dynamic HTML forms. Definitely more profit in this, for them.