SoylentNews is people
SoylentNews
Submitted via IRC for TheMightyBuzzard
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.
Source: http://www.ghacks.net/2017/01/29/google-removes-plugin-controls-from-chrome/
(Score: 2) by jmorris on Wednesday February 01 2017, @02:04AM
Google disconinued Chrome on my machine.
I'm running Devuan and Chromium 55 is in the repo for me. You weren't expecting the closed source Chrome in a Debian based distro, right? If you really want it there is a .deb available from Google. So unless you are still living in the dark ages with a 32bit machine you are good to go.
(Score: 2) by hendrikboom on Saturday February 04 2017, @03:49PM
Thanks for the reminder. Chromium now installed. I wasn't expecting it to stay around for my 32-bit machine after Google dropped 32-bit Chrome. Well, 32-bit Chrome still runs, but it is no longer updated or patched, so it is probably a security risk and I do not use it. But I see 32-bit Chromium is still advancing in version numbers, presumably in step with 64-bit chrome.