Closed
Bug 1239525
Opened 9 years ago
Closed 9 years ago
Tie asyncInit to !e10s
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(e10sm8+, firefox45 fixed, firefox46 fixed)
RESOLVED
FIXED
mozilla46
People
(Reporter: Felipe, Assigned: Felipe)
Details
Attachments
(1 file)
1.66 KB,
patch
|
bugzilla
:
review+
Sylvestre
:
approval-mozilla-aurora+
|
Details | Diff | Splinter 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)
Updated•9 years ago
|
tracking-e10s:
--- → m8+
Updated•9 years ago
|
Attachment #8707688 -
Flags: review?(aklotz) → review+
Comment 2•9 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8e03778117d3
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox46:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla46
Assignee | ||
Comment 3•9 years ago
|
||
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?
Updated•9 years ago
|
Attachment #8707688 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Assignee | ||
Comment 4•9 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/9b4cbc2f9fd6
status-firefox45:
--- → fixed
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
•