Skip to content
This repository has been archived by the owner on Nov 15, 2017. It is now read-only.

Support clikcable placeholders for plugins #41

Closed
gorhill opened this issue Nov 10, 2013 · 3 comments
Closed

Support clikcable placeholders for plugins #41

gorhill opened this issue Nov 10, 2013 · 3 comments

Comments

@gorhill
Copy link
Owner

gorhill commented Nov 10, 2013

Just like NoScript does -- one of its best feature.

I have no idea of feasability yet.

@insanitybit
Copy link

Isn't this natively supported through Click To Play plugins? Is there a way for you to simple manage the whitelist for that the way you do for Javascript?

@gorhill
Copy link
Owner Author

gorhill commented Nov 11, 2013

Problem is chrome API doesn't have a "click-to-play" setting (that would be great), it has only "allow" or "block":

http://developer.chrome.com/extensions/contentSettings.html#property-plugins

But yes, currently if the user choose "click-to-play" in chromium settings, and user whitelist, say, Youtube (and whatever else it needs to play videos), it starts to resemble the NoScript feature. But for HTTPSB this would still require at least two clicks to unblock a plugin, whereas with NoScript it is a single click feature, with no need to access the popup menu.

@gorhill
Copy link
Owner Author

gorhill commented Dec 24, 2013

Won't fix, Chromium has already a "click-to-play" feature, so it's just a matter of not blacklisting "plugin" and activating the "click-to-play" Chromium feature. I use it this way and it has been working fine, so I don't see the need to add more code (along with the issues/bugs) to replicate what is already built in the browser.

@gorhill gorhill closed this as completed Dec 24, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants