JEP Public Resource

Many add-on developer want to inject their own html file at some point to the content document via the content-script. Since these html files are stored under some resource:// based url, content iframes refuse to display them.

Goals

Provide a way for add-on developers to make some resource files of their add-on public (available for any content). Relevant chrome feature: http://developer.chrome.com/extensions/manifest.html#web_accessible_resources

Proposal

The best proposal so far is a custom protocol for these resources. We should check if there is any platform changes needed to enable an uri with custom protocol to be loaded by content, or the protocol can be defined in a way that platform changes are not required.

Relevant Bugs

https://bugzilla.mozilla.org/show_bug.cgi?id=792479

https://bugzilla.mozilla.org/show_bug.cgi?id=820213

Discussion

https://etherpad.mozilla.org/JEP-pub-res