chrome.contentSettings.plugins.set doesn't block the PDF plugin.
Reported by
rglee...@londontrustmedia.com,
Feb 21 2017
|
||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Steps to reproduce the problem:
1. From an extension, use chrome.contentSettings.plugins.set() to block the PDF plugin, using the "<all_urls>" pattern:
chrome.contentSettings.plugins.set({
primaryPattern: "<all_urls>",
resourceIdentifier: {id: "google-chrome-pdf"},
setting: "block",
scope: "regular"}, () => {
console.log("blocked")
})
2. Load a test page that embeds a PDF, such as http://plugindoc.mozdev.org/testpages/pdf.html
3. The PDF is embedded, but it should have been blocked.
What is the expected behavior?
The expected behaviour is that blocking the PDF plugin will stop PDF documents from being embedded onto a page.
What went wrong?
PDF plugin still runs even when contentSettings rule is defined to block it.
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 56.0.2924.87 Channel: stable
OS Version: OS X 10.12.3
Flash Version:
the only way i could reliably disable the PDF plugin on OSX is to go to chrome://settings/content and uncheck the "open PDF in PDF viewer" option.
,
Feb 22 2017
,
Feb 22 2017
,
Feb 22 2017
As per the comment#1 closing this issue for now. Please feel free to raise a new issue if you face the issue again on chrome. Thanks,
,
Feb 22 2017
Sorry, I think you misunderstood comment #1. I just corrected an error earlier in my report. The bug report is about the chrome extension API, chrome.contentSettings.plugins.set() is not having any effect against the PDF plugin. It does not block the plugin at all.
,
Feb 22 2017
And because of that, there is no way to disable it from the extension API. Please re-open, or advise of a solution. Thanks.
,
Feb 23 2017
Hi, I created a new issue, since I am getting no response here: https://bugs.chromium.org/p/chromium/issues/detail?id=695092 That issue also has no response. Comment #1 corrected my original bug report, it was not intended to be a solution. The bug report relates to chrome.contentSettings.plugins.set() specifically. There is no way to progmatically disable the PDF plugin. Are you implying that the PDF plugin cannot be blocked that API, by accepting comment #1 as a solution? Please have the courtesy to reply. Thank you.
,
Feb 23 2017
Since a new bug report has already been filed, let's just continue the discussion there. This indeed looks like a misunderstanding and the bug has been closed incorrectly. Please keep in mind some people triage hundreds of bugs a day, or they may be slow to respond for any number of reasons. The number of bug reporters vastly out number the number of people who respond, so please have patience.
,
Feb 24 2017
Apologies, I understand, thank you. |
||||
►
Sign in to add a comment |
||||
Comment 1 by rglee...@londontrustmedia.com
, Feb 21 2017