X
Tap here to go to the mobile version of the site.

Support Forum

Firefox pdf.js not working with clippers

Posted

Hello!

I'm using firefox dev edition, both Mendeley and Evernote addons have stopped working with PDF files.

I have reset the key "disable_full_page_plugin_for_types" in about:config (using right click > reset), because the value was "application/pdf" (now is blank) but I see no improvements.

When using the web version of the pdf.js both clippers work as expected https://mozilla.github.io/pdf.js/web/viewer.html

What am I doing wrong?

Hello! I'm using firefox dev edition, both Mendeley and Evernote addons have stopped working with PDF files. I have reset the key "disable_full_page_plugin_for_types" in about:config (using right click > reset), because the value was "application/pdf" (now is blank) but I see no improvements. When using the web version of the pdf.js both clippers work as expected https://mozilla.github.io/pdf.js/web/viewer.html What am I doing wrong?

Modified by amacs

Chosen solution

Firefox 60+ treats the built-in viewer as part of the browser ("chrome") and blocks extensions from injecting content scripts into the viewer. As you noted, the online demo is not affected because it is a pure web app.

You can use the web app to load local PDF files as a workaround (see https://support.mozilla.org/questions/1221277), but for PDFs on the web, I haven't thought of a fix.

Read this answer in context 1
jscher2000
  • Top 10 Contributor
8785 solutions 71851 answers

Chosen Solution

Firefox 60+ treats the built-in viewer as part of the browser ("chrome") and blocks extensions from injecting content scripts into the viewer. As you noted, the online demo is not affected because it is a pure web app.

You can use the web app to load local PDF files as a workaround (see https://support.mozilla.org/questions/1221277), but for PDFs on the web, I haven't thought of a fix.

Firefox 60+ treats the built-in viewer as part of the browser ("chrome") and blocks extensions from injecting content scripts into the viewer. As you noted, the online demo is not affected because it is a pure web app. You can use the web app to load local PDF files as a workaround (see [https://support.mozilla.org/questions/1221277]), but for PDFs on the web, I haven't thought of a fix.

Question owner

Hi! Thanks for the pretty quick reply!!

Mendeley support (where I was before investigating the issue) told me they've installed FF Dev Edition and the addon and it worked as expected, I thought it was just me because of that, so why doesn't this affect them?

Also, so what exactly the disable_full_page_plugin_for_types "application/pdf" key means?

And if I understand your post correctly, this is a 'feature' of 'chrome' and you guys are working on how to make it work again?

Thank you!

Hi! Thanks for the pretty quick reply!! Mendeley support (where I was before investigating the issue) told me they've installed FF Dev Edition and the addon and it worked as expected, I thought it was just me because of that, so why doesn't this affect them? Also, so what exactly the disable_full_page_plugin_for_types "application/pdf" key means? And if I understand your post correctly, this is a 'feature' of 'chrome' and you guys are working on how to make it work again? Thank you!

Modified by amacs

jscher2000
  • Top 10 Contributor
8785 solutions 71851 answers

Hi amacs, Mozilla browsers distinguish between the "content" and the "chrome"; another company liked this so much they named a bunch of products after it. But I digress.

Mendeley support (where I was before investigating the issue) told me they've installed FF Dev Edition and the addon and it worked as expected, I thought it was just me because of that, so why doesn't this affect them?

Good question. I don't use Developer Edition so I don't know whether there is a workaround in DE. Or possibly they didn't try the exact feature that isn't working for you?

Also, so what exactly the disable_full_page_plugin_for_types "application/pdf" key means?

This is obsolete now. It refers to plugins like the Adobe Acrobat plugin which could embed into a tab. Flash is the only plugin that could still do that and it doesn't handle PDFs.

Hi amacs, Mozilla browsers distinguish between the "content" and the "chrome"; another company liked this so much they named a bunch of products after it. But I digress. <blockquote>Mendeley support (where I was before investigating the issue) told me they've installed FF Dev Edition and the addon and it worked as expected, I thought it was just me because of that, so why doesn't this affect them?</blockquote> Good question. I don't use Developer Edition so I don't know whether there is a workaround in DE. Or possibly they didn't try the exact feature that isn't working for you? <blockquote>Also, so what exactly the disable_full_page_plugin_for_types "application/pdf" key means?</blockquote> This is obsolete now. It refers to plugins like the Adobe Acrobat plugin which could embed into a tab. Flash is the only plugin that could still do that and it doesn't handle PDFs.

Question owner

Hi amacs, Mozilla browsers distinguish between the "content" and the "chrome"; another company liked this so much they named a bunch of products after it.

lol, I feel you.

...or possibly they didn't try the exact feature that isn't working for you?

Donno, I even made a video for them, their reply was that they couldn't replicate it.

This is obsolete now.

Well, fml.

Good luck on sorting this out and thanks for the answers, you're awesome on this!

<blockquote> Hi amacs, Mozilla browsers distinguish between the "content" and the "chrome"; another company liked this so much they named a bunch of products after it. </blockquote> lol, I feel you. <blockquote>...or possibly they didn't try the exact feature that isn't working for you?</blockquote> Donno, I even made a video for them, their reply was that they couldn't replicate it. <blockquote>This is obsolete now. </blockquote> Well, fml. Good luck on sorting this out and thanks for the answers, you're awesome on this!