Closed
Bug 558196
Opened 15 years ago
Closed 12 years ago
High-overhead plug-ins should default to click-to-play
Categories
(Core Graveyard :: Plug-ins, enhancement)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: limi, Unassigned)
References
Details
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
Comment 1•12 years ago
|
||
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
Comment 2•12 years ago
|
||
Yeah, the CtP plans will fix this automatically.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•