Google Removes Plugin Controls From Chrome, Reports Claim (ghacks.net)

An anonymous reader shares a Ghacks report: 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. You can use it, among other things, 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.Further report on BetaNews.

Comments

Firefox cookie management, too

[FrankHaynes]

Firefox somewhere back in the low- to mid-40 version nummers eliminated the option to ask the user for each new cookie that sites try to set. This was valuable to anal-retentive users like me who could allow the target site and maybe its CDN to set cookies, but BIGINVASIVEADS.COM and TRACKYOUREVERYMOVE.NET would get nada.

Remember when these were the upstart, alternative browsers out to help the little guy?

Re:Firefox cookie management, too

[JohnFen]

Yes, that's a problem. However, there are FF add-ons that will bring that behavior back, such as Cookie Controller.

Plugins are not Extensions...

[mythosaz]

Important distinction:

chrome://plugins/ is where the internal PDF viewer is enabled or disabled.
chrome://extensions/ is where you put uBlock, or your corporate overlords install WebSense.

Plugins are moving to chrome://settings/content

That's it. INTERNAL PLUGINS ARE GETTING MOVED to a new menu location.