Closed
Bug 1040158
Opened 10 years ago
Closed 10 years ago
Need a way to override multiprocessCompatible flag in install.rdf (AMO control for e10s-breaking add-ons)
Categories
(Firefox :: Extension Compatibility, defect)
Firefox
Extension Compatibility
Tracking
()
People
(Reporter: billm, Assigned: mossop)
References
Details
Attachments
(1 file)
21.20 KB,
patch
|
Unfocused
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #1029926 +++ Blair asked for some follow-up work to bug 1029926, which added the multiprocessCompatible flag to install.rdf: In addition to supporting this flag in install.rdf, we'll also want a followup bug to let AMO override it. This will let us cover cases like: * Add-on is multi-process compatible, but author didn't add multiprocessCompatible to install.rdf * Add-on specifies multiprocessCompatible, but we find it's buggy and needs the shims afterall * Something changes that makes an add-on that was once multi-process compatible now be broken and need shims And, finally, we should have some telemetry added for this, so we know what impact it's having now and over time.
Reporter | ||
Updated•10 years ago
|
No longer blocks: e10s-m1, e10s-shims
Updated•10 years ago
|
Blocks: e10s-addons
tracking-e10s:
--- → ?
Depends on: 1029926
Summary: Need a way to override multiprocessCompatible flag in install.rdf and collect telemetry for it → Need a way to override multiprocessCompatible flag in install.rdf and collect telemetry for it (AMO control for e10s-breaking add-ons)
Assignee | ||
Updated•10 years ago
|
Flags: firefox-backlog+
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → wmccloskey
Assignee | ||
Updated•10 years ago
|
Points: --- → 5
Flags: qe-verify-
Assignee | ||
Comment 2•10 years ago
|
||
I can't see how this depends on bug 1083545
No longer depends on: 1083545
Assignee | ||
Updated•10 years ago
|
Assignee: wmccloskey → dtownsend
Status: NEW → ASSIGNED
Iteration: --- → 38.2 - 9 Feb
Assignee | ||
Comment 3•10 years ago
|
||
I'm splitting the telemetry piece of this off into bug 1128121
Summary: Need a way to override multiprocessCompatible flag in install.rdf and collect telemetry for it (AMO control for e10s-breaking add-ons) → Need a way to override multiprocessCompatible flag in install.rdf (AMO control for e10s-breaking add-ons)
Assignee | ||
Comment 4•10 years ago
|
||
This allows an update.rdf to override the multiprocessCompatible. It doesn't do this at install time since we don't always load the update.rdf then (perhaps we should). But whenever a daily update check happens the change will be applied and persisted. The format is simple, with no flag present in update.rdf no change happens. If the flag is set then its value overrides that of install.rdf.
Attachment #8558182 -
Flags: review?(bmcbride)
Comment 5•10 years ago
|
||
(In reply to Dave Townsend [:mossop] from comment #4) > It doesn't > do this at install time since we don't always load the update.rdf then > (perhaps we should). Yea, have been thinking we should.
Updated•10 years ago
|
Attachment #8558182 -
Flags: review?(bmcbride) → review+
Assignee | ||
Comment 6•10 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/3c49c72bbd26 (In reply to Blair McBride [:Unfocused] (I don't read bugmail - needinfo? me!) from comment #5) > (In reply to Dave Townsend [:mossop] from comment #4) > > It doesn't > > do this at install time since we don't always load the update.rdf then > > (perhaps we should). > > Yea, have been thinking we should. Filed bug 1129479
Assignee | ||
Comment 7•10 years ago
|
||
Backed out for test failures: https://hg.mozilla.org/integration/fx-team/rev/584d995002a6
Assignee | ||
Comment 8•10 years ago
|
||
Relanded with the braindead simple initialisation order change in the test: https://hg.mozilla.org/integration/fx-team/rev/d0d66a5cad38
Comment 9•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/d0d66a5cad38
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox38:
--- → fixed
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → Firefox 38
You need to log in
before you can comment on or make changes to this bug.
Description
•