Changes

Jump to: navigation, search

Opt-in activation for plugins

2 bytes added, 01:23, 1 March 2012
no edit summary
* Whether to differentiate between an SSL site containing plugin content loaded over SSL and an HTTP site containing plugin content loaded over HTTP. Trusting content served over HTTPS is not the same as trusting content over HTTP, which is why they are usually treated as separate origins for security purposes.
* Risk of clickjacking - is this something we should try to mitigate?
|Feature overview=Unknown, slow or insecure plugins shouldn't be allowed to run without user interaction.
Confirm
197
edits

Navigation menu