Issue metadata
Sign in to add a comment
|
In chrome extension API - chrome.contentSettings["plugins"].set not applied to opened tabs until navigating away to a different domain and returning to the current domain (or opening a new tab)
Reported by
c...@funtomic.com,
Jan 10 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.51 Safari/537.36 Steps to reproduce the problem: 1. Open a tab with https://helpx.adobe.com/flash-player.html 2. Manually block Flash plugin for this domain 3. Enable Flash for helpx.adobe.com from a chrome extension, example: chrome.contentSettings["plugins"].set({ 'primaryPattern': "*://helpx.adobe.com/*", 'setting': "allow", 'scope': ('regular') }, function(){}); 4. Reload the page and see that the Flash animation still doesn't work and Flash isn't detected by the page (although you can see Flash is enabled by an extension in the little 'i' sign in the address bar) 5. On the same tab, navigate to www.google.com and go back - the animation works , Flash is detected by the page 6. Opening a new tab with the same url would also work What is the expected behavior? Flash plugin should be enabled on the same tab after reloading the page (same as when changing the settings manually and not from Extension API) What went wrong? Although the page was refreshed, Flash plugin remained blocked until navigating away to another domain or opening a new tab Did this work before? N/A Does this work in other browsers? Yes Chrome version: 56.0.2924.51 Channel: beta OS Version: OS X 10.11.6 Flash Version: 24.0.0.194 There is a similar, however *different*, bug - for incognito scenario - https://bugs.chromium.org/p/chromium/issues/detail?id=494501#
,
Jul 6 2017
,
Jul 6 2017
,
Jul 9
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 9
Still available, but not particularly high priority. Updating labels.
,
Jul 12
The issues seems to be resolved. I tried both cases, allowing manual and blocking by extension, and blocking manual and allowing by extension. In both cases, extension's choice was applied.
,
Jul 16
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by msramek@chromium.org
, Jan 10 2017Components: Privacy
Labels: -OS-Mac OS-All
Status: Available (was: Unconfirmed)