New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 603683 link

Starred by 4 users
Status: Fixed
Owner:
georgesak@chromium.org
Closed: Apr 2017
Cc:
zmin@chromium.org
█ kotah@chromium.org
█ blumberg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Feature



Sign in to add a comment

[FR] More fine-grained per-plugin controls on DefaultPluginsSetting

Reported by peter.ki...@gs.com, Apr 14 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36

Steps to reproduce the problem:
When Plugins are set to "Let me choose when to run plugin content" and individual user can then uncheck "Always allowed to run" for Adobe Flash Player only, effectively setting Flash as as Click to Play, while allowing the other plugins (e.g. Chrome PDF Viewer) to auto-run.

What is the expected behavior?

What went wrong?
We can use the DefaultPluginsSetting policy to set all plugins to "Click to Play". However, we need to only set Flash as "Click to Play".

Did this work before? N/A 

Chrome version: 49.0.2623.112  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by vssummer...@gmail.com, Apr 17 2016 

You can check to see if your browser flags are correct for it's manner.

Comment 2 by peter.ki...@gs.com, Apr 18 2016 

Browser flags? Not sure what you mean.

Comment 3 by dskaram@chromium.org, Apr 22 2016

Labels: -Type-Bug Type-Feature
Owner: georgesak@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: [FR] More fine-grained per-plugin controls on DefaultPluginsSetting (was: Enterpise policy (GPO) to set Adobe Flash Player as Click to Play)
+Geroges, please prioritize and assign.

Comment 4 by peter.ki...@gs.com, May 16 2016 

Any update on this?

Comment 5 by georgesak@chromium.org, May 16 2016

Labels: -Pri-2 OS-Chrome OS-Linux OS-Mac Pri-3
Status: Available (was: Assigned)
Not yet. I want to make sure I understand the request first: You want to be able to set a DefaultPluginsSetting for individual plugins, such as flash?

Comment 6 by peter.ki...@gs.com, May 16 2016 

Exactly. When we change DefaultPluginsSetting to 3 in order to set Flash click-to-play,  the PDF Viewer plugin is also getting flipped to click-to-play, which is not ideal. 

Glad to provide any additional details needed.

Comment 7 by georgesak@chromium.org, May 17 2016 

Got it thanks.

Comment 8 Deleted

Comment 9 by zmin@chromium.org, Jun 30 2016

Cc: zmin@chromium.org
CORRECT: There will be a Flash only setting but it won't happen until around M54. However, you can still use DefaultPluginsSetting for Flash right now(M51) because PDF viewer is set to "Always allowed to run" by default.

Comment 10 by blumberg@chromium.org, Jun 30 2016

Cc: blumberg@chromium.org
Status: Started (was: Available)
In progress...

Comment 11 by kotah@chromium.org, Apr 10 2017

Cc: kotah@chromium.org
Labels: Hotlist-Enterprise
We have another enterprise customer requesting for per-plugin controls specific to Flash.

Does DefaultPluginsSetting / PluginsAllowedForUrls / PluginsBlockedForUrls only affects Flash now, or could it affect other plugins and is this feature request still open?

Comment 12 by lafo...@chromium.org, Apr 10 2017 

It only affects Flash Player, the last remaining plugin.

Comment 13 by georgesak@chromium.org, Apr 11 2017

Status: Fixed (was: Started)
Closing this as fixed.

Comment 14 by kathrelk...@chromium.org, Jun 5 2017

Labels: M-54

Comment 15 by jingwee@chromium.org, May 2 2018

Labels: cros-verified
Verified working for ChromeOS with M66.0.3359.149 10452.81.0 stable paine.
►

Sign in to add a comment