Jump to content

Google removes Plugin controls from Chrome


Petrovic

Recommended Posts

Google made a change in Chrome 57 that removes options from the browser to manage plugins such as Google Widevine, Adobe Flash, or the Chrome PDF Viewer.

 

If you load chrome://plugins in Chrome 56 or earlier, a list of installed plugins is displayed to you. The list includes information about each plugin, including a name and description, location on the local system, version, and options to disable it or set it to "always run".

 

You can use it to disable plugins that you don't require. While you can do the same for some plugins, Flash and PDF Viewer, using Chrome's Settings, the same is not possible for the DRM plugin Widevine, and any other plugin Google may add to Chrome in the future.

 

Starting with Chrome 57, that option is no longer available. This means essentially that Chrome users won't be able to disable -- some -- plugins anymore, or even list the plugins that are installed in the web browser.

 

Please note that this affects Google Chrome and Chromium.

Google removes Plugin controls from Chrome

chrome plugins

This goes hand in hand with a change in Chrome 56 that saw plugins getting re-enabled on restart automatically, and without you being able to do anything about that either.

Technically with the latest changes to the plugins handling code all plugins will be in the "enabled" state as seen on the chrome://plugins page.

To sum it up:

  1. chrome://plugins is deprecated in Chrome 57.
  2. Only Flash and the PDF Viewer can be controlled via the Chrome Settings.
  3. All other plugins cannot be controlled anymore by the user.
  4. Disable plugins like Flash or Widevine are re-enabled in Chrome 56 after restarts.

 

You have to dig deep on the Chromium bugs website to find information on those changes. This bug highlights that chrome://plugins is deprecated, and that plugin control access has been removed from Chrome with the exception of Adobe Flash and PDF Viewer.

 

One issue when it comes to disabling Flash is that Chrome handles Flash content differently depending on where it was disabled.

If you disable Flash on chrome://plugins, Flash is completely disabled. If you use the Settings instead, you get a square asking whether you want to enable Flash to play content instead.

 

Users may overcome this by enabling this flag: chrome://flags/#prefer-html-over-flash

This bug highlights that Google considers all plugins but Flash and the PDF Viewer, as integral parts of the Chrome browser, and that it does not want users to disable those.

All other plugins (NaCL and WideVine) are considered integral part of the browser and can not be disabled.

Temporary Solution

The only option that is left is to delete the plugin folder on the local system. The caveat is that it gets added again when Chrome updates.

The location is platform specific. On windows, it is located here: C:\Program Files (x86)\Google\Chrome\Application\[Chrome Version]\WidevineCdm\.

Close Chrome, delete the folder, and restart the browser. The plugin is no longer loaded by Chrome. you do need to repeat this whenever Chrome updates though

Article source

Link to comment
Share on other sites


  • Replies 7
  • Views 1.5k
  • Created
  • Last Reply
  • Administrator

This is quite wrong decision by Google, I feel. Just because you do not want people to do things does not mean you take away it's control from the expert users I think.

Link to comment
Share on other sites


https://i.imgsafe.org/0adbdf03a2.png

 

i test  Chromium 58  it still have  chrome://flags/  were you can enable or disable a bunch of stuff  Flash in Chromium for windows has too be installed its not like Google Chrome and besides  you can still go too chrome://flags/ and turn it off. .

 

You can download Chromium with or without Widevine  its open source just like you can download Firefox EmE free .

Link to comment
Share on other sites


Now You can test also Google Chrome 58.0.3000.4 Dev.  NB! If someone wishes to make a separate topic, please to do it.


Google Chrome 58.0.3000.4 Dev

x86
http://redirector.gvt1.com/edgedl/release2/zb2eyzakcsq6gauw7t9mzaeoe99f9fyzp0s8epn7m6731cqegr2cischf91saudujko7cygxn66wqkjge9rmpj3hwwtw0ed7w5r/58.0.3000.4_chrome_installer.exe
MD5 - 46736398A2870747CE124F2083844328

x64
http://redirector.gvt1.com/edgedl/release2/9tmz5xlhis4gbeogtfceoj4jwwc0mb9ksr7cw4ne1p0e515ph3t4l38k4i619m9n3v8q3t29zwxtcp1zx3wj3rorexxi3xquqx1/58.0.3000.4_chrome_installer.exe
MD5 - 7A49343EB65796A2E5BBE0A4A9C1497A


Portable:

x86
https://mega.nz/#!MhZ33T6K!r6Tk9wb_-fnBdzIdZ8e4fd7yKjr4GPA1R5Df77tnOYg
x64
https://mega.nz/#!N1xiHB7I!PbKDtYWO6De9znrfBYoO8_xerr0T0OFrxxCQZDSYbEQ

 

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...