Closed
Bug 850449
Opened 13 years ago
Closed 13 years ago
Expose 'addon' to scripts matching custom addon-page URIs
Categories
(Add-on SDK Graveyard :: General, defect, P1)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: KWierso, Unassigned)
References
Details
Attachments
(1 file)
It'd be nice to expose the addon object to page scripts similar to trusted page content in panels, so the scripts can communicate back to the main addon script without attaching a content script.
Updated•13 years ago
|
Assignee: nobody → poirot.alex
Comment 2•13 years ago
|
||
Myk, would something like this ease the usage of addon-page?
We are automagically exposing an `addon` global object that act exactly like `self` in content scripts but injected directly into all addon page documents.
Then you can send and receive page events with :
let page = require("sdk/addon-page");
page.on("message",...);
page.postMessage()
page.port.on(...);
page.port.emit(...);
Irakli, Would you bless such new high-level feature?
Attachment #724213 -
Flags: feedback?(rFobic)
Attachment #724213 -
Flags: feedback?(myk)
Comment 3•13 years ago
|
||
Comment on attachment 724213 [details]
Pull request 851
Yes, that would indeed make addon-page easier to use! It would enable me to eliminate a whole layer of the stack.
Attachment #724213 -
Flags: feedback?(myk) → feedback+
| Reporter | ||
Updated•13 years ago
|
Priority: -- → P1
Updated•13 years ago
|
Attachment #724213 -
Flags: feedback?(rFobic) → feedback-
Comment 4•13 years ago
|
||
Looks like addon-page is going to be dropped in australis so we probably don't need to work on this bug anymore
Assignee: poirot.alex → nobody
Depends on: 873102
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•