You are not logged in.
Pages: 1
I vote do not enable user extensions in the Epic. Thanks!
NPAPI is on its deathbed...
http://blog.chromium.org/2013/09/saying … npapi.html
The answer has already been given as a built-in feature of Chromium:
chrome://settings/content
Disable JS globally, allow exceptions otherwise. No extension needed. As a matter of fact, I have all settings on that page disabled.
And the settings are not buried deep at all. On the contrary, if you need to re-enable settings per site, click small icon to the left of the URL in the omnibox and enable them there.
Chromium is even killing NPAPI plugins this year. (Re: Adobe Flash NPAPI plugin...)
http://blog.chromium.org/2013/09/saying … npapi.html
Add me to the small informed chorus of folks suggesting that the Epic staff not start adding a bunch of plugins. And to the masses here that seem to insist on plugins, make a choice: Privacy, or Convenience. You cannot have both.
I completely agree with weathertop. Keep Epic's original design goals and do not allow user-installed extensions or plugins. Actually, the first thing I do with a new browser install (Chrome, Chromium, Firefox, etc) is disable all plugins and extensions. Then only enable/add the few that I require.
Actually, perhaps Epic should consider disable everything by default under chrome://plugins be default? e.g. Adobe Flash has been shown to be the worst privacy offender.
http://www.welivesecurity.com/2010/10/0 … er-part-1/
Thank you.
Pages: 1