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

Issue 702985 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , All , Chrome , Mac
Pri: 1
Type: Bug

Blocking:
issue 696790



Sign in to add a comment

Add support for universal wildcard site exceptions (for Flash content)

Project Member Reported by lafo...@chromium.org, Mar 19 2017

Issue description

As we move to simplify the control options for consumers, from 3 options (Always, Ask, Block) down to 2 (Ask, Block) it will be necessary to give Enterprises and (potentially) power users a way to do have something functionally equivalent to Always allow.

To support equivalent functionality we could add support for universal wildcards (i.e. "[*.]" w/ no domain suffix) to the Flash exceptions.  The configuration could be limited strictly to the policy(1), for Enterprise admins, or it could be added to the UI, for consumer users.

My inclination would be to only support the Enterprise case, since that will be a blocker to shipping a unified setting, but I'm open to both.

(1) - https://www.chromium.org/administrators/policy-list-3#PluginsAllowedForUrls
 
Components: Enterprise Internals>Plugins>Flash
FWIW, I confirmed on my home PC that this does not work today.

Comment 2 by ihf@chromium.org, Mar 20 2017

Cc: dkalin@chromium.org krishna...@chromium.org
Status: WontFix (was: Untriaged)
We were able to confirm that it is indeed possible to set global allows:

"https://*" and "http://*" are valid exception patterns.

There is no additional work required here.

Sign in to add a comment