New issue
Advanced search Search tips

Issue 685590 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 673199
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Previously disabled plugins suddenly enabled after updating to Chrome 56

Reported by jviide...@gmail.com, Jan 26 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.76 Safari/537.36

Steps to reproduce the problem:
1. With Chrome 55.0.2883.95 disable plugins (e.g. Flash, Widevine, Native Client) from chrome://plugins
2. Update to Chrome 56.0.2924.76.
3. Go to chrome://plugins, observe the previously disabled plugins to be enabled again.

What is the expected behavior?
Previously disabled plugins should stay disabled over Chrome updates.

What went wrong?
Previously disabled plugins did not stay disabled over the update from Chrome 55.0.2883.95 to Chrome 56.0.2924.76.

The attached screenshots are from an attempt to reproduce this issue. The screenshot with disabled plugins is the Chrome 55 chrome://plugins page, the other one is taken right after updating to Chrome 56.

Did this work before? N/A 

Chrome version: 56.0.2924.76  Channel: stable
OS Version: OS X 10.12.3
Flash Version: 24.0.0.194
 

Comment 1 by jviide...@gmail.com, Jan 26 2017

The attached files lacked proper file extensions. Re-attached fixed versions to this comment. Sorry.
chrome 55.png
100 KB View Download
chrome 56.png
92.1 KB View Download

Comment 2 by jviide...@gmail.com, Jan 26 2017

Issue https://bugs.chromium.org/p/chromium/issues/detail?id=685597 paints a more accurate picture. It appears that Chrome 56 re-enabled plugins after every restart.
Labels: Prestable-56.0.2924.76 Needs-Triage-M56

Comment 4 by dhw@chromium.org, Jan 26 2017

Cc: pastarmovj@chromium.org
Components: Internals>Plugins
Status: Untriaged (was: Unconfirmed)
@pastarmovj, this issue says "all disabled plugins".  Is this just an expanded duplicate of  Issue 673199  ?
Mergedinto: 673199
Status: Duplicate (was: Untriaged)
Yes it is. 

Sign in to add a comment