Closed
Bug 553146
Opened 15 years ago
Closed 14 years ago
Figure out how to inject a Jetpack's context into HeadsUpDisplay console
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ddahl, Assigned: ddahl)
References
Details
We should do some hacking to see how we can use the new DevTools Heads Up Display (console) with a jetpack's JS context
See bug 534398
Assignee | ||
Comment 1•15 years ago
|
||
as of now, the Heads Up Display is just working inside of Firefox (trunk 1.9.3) - I have added a windowObserver that initializes the console and heads up display based on applicaiton ID, Jetpack should also have its own "hook" to start (perhaps a stand-alone window) console in the context of it's objects.
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → ddahl
Updated•15 years ago
|
Hardware: x86 → All
Assignee | ||
Updated•15 years ago
|
Priority: -- → P2
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
Comment 3•14 years ago
|
||
After discussion in the triage meeting, it seems like we need to take a step back and have a broader discussion about what Jetpack debugging tools will look like before filing and working on specific bugs around it such as this one.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•