Comment 321 for bug 263435

First of all, there will always be bad plugins, or bad usage of good plugins, or whatever. Some sites will always try to misuse all available possibilities.

Now we have the pop-up blocker, am I right?
Why, instead of making it, don't we endlessly discuss "some pop-ups are legitimate ones, we cannot hurt them, etc"?

So, bad plugins will always exist, they will report "I am good plugin", they will return 0x100-the-magic-number, and yet they will behave badly -- eat all the keys as an example.

Well, the proposed solution:

The control at the plugin-type level: global settings like "I want this plugin to handle keys before the browser, and that plugin to receive them after the browser". We can even set these to "plugin is the boss" by default, but, at least, let's give the power users an ability to control it.

The next level: for untrusted plugins, the ability of (temporarily) enabling key-swallowing for a particular instance of the plugin -- yes, this is about "my favourite flash game".

I thought about Quakelive -- an extreme case of "browser plugin". Why do we call such things "plugins", I don't know. It can do anything, format your hard-drive, for example. Any exploit found in such "plugins" -- and your computer is dead.

P.S. About "don't install bad plugins" -- sounds like "don't browse sites with bad pop-ups" -- there is no need for the pop-up blocker. People want to watch youtube and yet they want to create a new tab with Ctrl-T, strangely.