Re: Plugin whitelist

On 3/4/2014 3:05 PM, Bill Selman wrote:
> Java has a different reach than other plugins and is used for 
> different kinds of functionality. Can you share how your confidence 
> for this design translates to other plugins and their uses?

Top plugins by reach are:

* Flash (unaffected by any of this)
* Java (already affected, sometimes used invisibly)
* Silverlight (almost always visible, works fine)
* Unity (always visible, works fine)
very small minorities

The primary pain points in the original study were that nobody could 
understand why they had to click twice on videos (once to enable the 
plugin and once to play the video) and they really wanted a way to just 
say "yes always for this site" which was present but not discoverable. 
By switching things to be per-domain by default, the default interaction 
model is now the one users expect which is "yes please allow this plugin 
and stop asking me".

--BDS