Closed
Bug 1129664
Opened 10 years ago
Closed 8 years ago
[e10s] Find which low-level SDK modules are not e10s-compatible
Categories
(Add-on SDK Graveyard :: General, defect, P1)
Add-on SDK Graveyard
General
Tracking
(e10s+)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: mossop, Unassigned)
References
Details
We don't know which are and aren't at the moment. Most probably already are, many can be made to be so, a few cannot be e10s compliant and so should probably be replaced.
Reporter | ||
Updated•10 years ago
|
tracking-e10s:
--- → +
Updated•10 years ago
|
Priority: -- → P1
Comment 1•9 years ago
|
||
adding to short list of bugs i want to find plan for or status
Flags: needinfo?(sescalante)
Comment 2•8 years ago
|
||
the focus is on high level API compatibility - using hybrid add-on in meantime for migration as more functionality comes in webextensions. to use as much new technology as possible and call back only when needed.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(sescalante)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•