Comment #16 on issue 736 by ida...@chromium.org: No way to disable plugins
using UI
http://code.google.com/p/chromium/issues/detail?id=736
@jmccaskey:
Indeed the about:plugins seems like a great place for this. I think we
could do
something where each plugin can be enabled, disabled or made click-to-run.
This
would give the benefits of only being able to run plugins on demand for the
ones
that are needed rather than risking security by enabling fully or risking
things
not working be disabling fully as well. Plus since plugins are not
installed into
Chrome explicitly, it is nice to have a way to disable one so that it is
not used
in Chrome.
See the attached files for how this could look:
Attachments:
AboutPlug-ins_mockup.htm 9.8 KB
plugins.css 3.0 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
