Certain plug-ins that have a high startup cost should default to click-to-play mode. The most obvious example is the Java plug-in, which launches a 20MB+ Java Virtual Machine when loading a page. It should be easy to opt-in to always running it, but it shouldn't be the default. Something like this: Activate Java Plug-in [ ] Always activate Java Plug-in

I think we may not want to investigate given the current plans to * make most plugins click-to-play * have plugins instantiate async if web-compat allows

Yeah, the CtP plans will fix this automatically.