Closed
Bug 1268716
Opened 9 years ago
Closed 9 years ago
Plugin block list blocks SWF network requests, but does not prevent plugin instantiation (e10s-compatible fix for Aurora 48+)
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(e10s-, firefox46 unaffected, firefox47 wontfix, firefox48 affected, firefox49 affected)
RESOLVED
DUPLICATE
of bug 1268120
Tracking | Status | |
---|---|---|
e10s | - | --- |
firefox46 | --- | unaffected |
firefox47 | --- | wontfix |
firefox48 | --- | affected |
firefox49 | --- | affected |
People
(Reporter: cpeterson, Assigned: tschneider)
References
Details
+++ This bug was initially created as a clone of Bug #1266889 +++
We don't want to load the plugin when we're going to block the SWF anyways. We need to check the block list before instantiating the plugin.
The plugin instantiation fix in bug 1266889 is not e10s-compatible, but that is OK for Beta 47 when e10s is not enabled. We need an e10s-compatible fix for Aurora 48+, where e10s is enabled by default.
![]() |
||
Updated•9 years ago
|
tracking-e10s:
--- → -
Reporter | ||
Comment 1•9 years ago
|
||
Tobias said he will add an end-to-end test to verify that plugin instantiation blocking actually works, instead of just testing channel classification.
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•