Closed
Bug 593908
Opened 14 years ago
Closed 14 years ago
make tabs module e10s-compatible
Categories
(Add-on SDK Graveyard :: General, defect, P1)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
0.8
People
(Reporter: myk, Assigned: irakli)
References
Details
We need to make the tabs module e10s-compatible. At first glance, I think this just requires removal of the contentWindow and contentDocument accessors along with the three related event properties onReady, onLoad, onPaint. Benjamin: does that sound right? (See <https://jetpack.mozillalabs.com/sdk/0.7/docs/#module/jetpack-core/tabs> for docs on the API.) Dietrich: is this something you can take on?
Comment 1•14 years ago
|
||
If Warner and I get done with bug 567703 as early as we think we will, we can start working on this as one of the first modules to get ported to e10s-land.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → rFobic
Reporter | ||
Comment 2•14 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Version: Trunk → unspecified
Assignee | ||
Comment 3•14 years ago
|
||
The work for this bug is done in the linked dependency. One it's fixed this will be resolved automatically.
Status: NEW → ASSIGNED
Assignee | ||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•