Closed
Bug 1129206
Opened 9 years ago
Closed 9 years ago
jpm should let developers disable e10s compatibility shims
Categories
(Add-on SDK Graveyard :: General, defect, P1)
Add-on SDK Graveyard
General
Tracking
(e10s+)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| e10s | + | --- |
People
(Reporter: wbamberg, Assigned: evold)
Details
To test that an add-on is multiprocess compatible a developer can set multiprocessCompatible[1] in the install.rdf. In the SDK, if you are using cfx you can hack this by editing the install.rdf template in the SDK installation. But this does not work for jpm. [1] https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#multiprocessCompatible
|
||
Updated•9 years ago
|
tracking-e10s:
--- → +
|
Assignee | |
Updated•9 years ago
|
Priority: -- → P1
|
|
Assignee | |
Comment 1•9 years ago
|
||
Would it make sense to make this a permission (listed in package.json)?
Flags: needinfo?(dtownsend)
|
|
Assignee | |
Comment 3•9 years ago
|
||
Resolved by https://github.com/mozilla/jpm/commit/316d282c406890ac0c7e86e0e1abfbaee5c2eaec
Assignee: nobody → evold
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•