Confirm
717
edits
Changes
no edit summary
* Manage plugin run settings on a per-site basis
* Control plugins on a per-plugin basis for a given site
* Mitigate attacks where user chooses to interact interacts with site (clickjacking, or simply wants to run vulnerable plugin)
|Feature non-goals=We can't prevent users getting owned up by vulnerable plugins if they choose to activate a plugin on a site hosting malicious payloads. That is why driving plugin updates is important.
|Feature ux design=When plugins are found on a page, their start up will be delayed until a user performs interaction with the browser to enable the running of the plugin.
