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 Arik on Tuesday January 31 2017, @04:06PM
Use links.
If laughter is the best medicine, who are the best doctors?
(Score: 0) by Anonymous Coward on Tuesday January 31 2017, @04:44PM
At this point the only thing it accumulates from firefox is security fixes.
(Score: 3, Informative) by Anonymous Coward on Tuesday January 31 2017, @04:51PM
From their FAQ: [palemoon.org]
Note that Pale Moon will never adopt the Australis (Firefox 29 and later) interface and aims to remain a fully XUL-driven browser with full user interface customizability.
And also later on the same page [palemoon.org] (emphasis by me):
Pale Moon is most certainly not "just a rebuild" of existing Firefox code, unlike other "alternative" Firefox browsers out there. As Pale Moon has developed, so has the amount of individual code for the browser, steadily diverging Pale Moon from its sibling in the direction aimed for in this browser - having transformed it from an optimized build (which it was when it first started out in 2009) into a true "fork" of Mozilla code and being completely independent now.