Google Chrome Eliminates the Possibility of Controlling Our Plugins

0
390
Google Chrome 56
Spread the love

Google Chrome

Google Chrome has snatched the feature with which we used to control our plugins. With the new update Google increasingly offers less advanced control to users over Chrome.

Extensions or plugins are small applications developed to increase the functionality of major browsers today. Today, practically all web browsers are compatible with different extensions or plugins that allow users to customize and provide them with the functions they want, however, in addition to custom extensions, some browsers such as Google Chrome come with extensions by default, which are part of the browser’s out-of-the-box experience.

If we have any version of Google Chrome type in “chrome: // plugins /”, we can see how the browser opens an internal configuration page from which we will see a series of internal add-ons, PDF documents or the Flash plugin. From there we can see in detail those components and even disable them so that they are not part of our browser.

Recently, Google has introduced a new change in its browser, which will come with Google Chrome 57, which will prevent users from configuring and managing these components. This way, users of the next version who try to access the previous plugins configuration page will see how the browser returns a 404 error indicating that the page is not available.

Many users of Google Chrome 56, the latest version released last week, have seen how some plugins, once deactivated were re-activated on their own. From the next version, all these plugins will always be activated by default and, in addition, users will not be able to do anything to avoid it.

However, some plugins such as Adobe Flash and PDF Viewer will be able to be controlled from the browser settings menu, although others, such as Widevine or DRM support, we will not be able to control.

However, if we deactivated the plugin from the “plugins” section it was completely disabled, if we do it from the browser configuration this is not going to be so, but that Flash will still be loaded in memory and the only thing different will be that when we want to enter the specific page with this type of content, we will see a warning.

There is a temporary solution to this Google Chrome limitation

If for some reason we want to permanently remove any component of the browser, we can still do so by removing it completely from our computer. To do this, simply go to the installation path of the browser:

C: \ Program Files (x86) \ Google \ Chrome \ Application \ [browser version] \

Here we eliminate that entry. The component will no longer exist and therefore will not load, at least until Chrome is refreshed again.

LEAVE A REPLY

Please enter your comment!
Please enter your name here