Closed
Bug 983928
Opened 11 years ago
Closed 10 years ago
Make protocol.js usable from content privileged code
Categories
(Add-on SDK Graveyard :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: irakli, Unassigned)
References
Details
Attachments
(1 file)
Given that add-on pages don't have chrome privileges it would make a lot of sense to make version of protocol.js that can be loaded in a content page & given a [MessagePort](http://www.w3.org/TR/webmessaging/#messageport) representing remote debugging protocol connection to a debuggee it should be able to generate high level OOP style API that could be used by add-on's.
Reporter | ||
Comment 1•11 years ago
|
||
In order to generate high level APIs dynamically from a raw connection we would need a way for actors to describe themselves. My understanding is that Bug 983331 does exactly that.
Depends on: 983331
Reporter | ||
Updated•11 years ago
|
Blocks: devtools-sdk
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Priority: -- → P1
Comment 3•10 years ago
|
||
Comment on attachment 8418225 [details] [review] Client side extraction from protocol.js Let's get this landed so we can iterate.
Attachment #8418225 -
Flags: review?(dcamp) → review+
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•