Issue 756066 link

Starred by 2 users

Issue metadata

Status:	Assigned
Owner:	georgesak@chromium.org
Cc:	pastarmovj@chromium.org ligim...@chromium.org █ blumberg@chromium.org
Components:	Enterprise
EstimatedDays:	----
NextAction:	----
OS:	Windows
Pri:	2
Type:	Bug
Arch-x86_64 Via-Wizard-Enterprise Needs-Triage-M60

Will PluginsAllowedForUrls supercede Non-Persisted HTML5 by Default ?

Reported by mayer...@gmail.com, Aug 16 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
N/A

What is the expected behavior?

What went wrong?
Will the policy to allow plugins for urls supersede the upcoming Chrome 66 Non-Persisted HTML5 by Default changes?

Did this work before? N/A 

Chrome version: 60.0.3112.90  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: