Closed Bug 1239525 Opened 4 years ago Closed 4 years ago

Tie asyncInit to !e10s

Categories

(Core :: Plug-ins, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla46
Tracking Status
e10s m8+ ---
firefox45 --- fixed
firefox46 --- fixed

People

(Reporter: Felipe, Assigned: Felipe)

Details

Attachments

(1 file)

Attached patch patchSplinter Review
While async plugin init shouldn't be used together with e10s, we should make sure it is disabled while e10s is on. The prefs could easily get out of sync, so it's best to make sure the mismatch never happens.
Attachment #8707688 - Flags: review?(aklotz)
Attachment #8707688 - Flags: review?(aklotz) → review+
https://hg.mozilla.org/mozilla-central/rev/8e03778117d3
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla46
Comment on attachment 8707688 [details] [diff] [review]
patch

Approval Request Comment
[Feature/regressing bug #]: async plugin initialization
[User impact if declined]: this patch is necessary for the e10s experiment that we will run on beta 45. it makes sure that async plugin initialization is off for users who get e10s toggled on.
[Describe test coverage new/current, TreeHerder]: landed on central
[Risks and why]: no risks
[String/UUID change made/needed]: no strings
Attachment #8707688 - Flags: approval-mozilla-aurora?
Attachment #8707688 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
You need to log in before you can comment on or make changes to this bug.