1087637 - Make Cross domain XHR easier for panels inside SDK addons

Status: RESOLVED WORKSFORME

(Add-on SDK Graveyard :: General, defect)

Description

[Tim Nguyen :ntim]

I'm quite surprised that panels by SDK addons have the same level of privilege as a simple webpage. Cross domain XHR should be available without the hassle of using contentScripts inside the panels. Of course, the cross domain XHRs would be limited to what's specified in the manifest. 

This would make porting Chrome addons to Firefox much easier.

Comment 1

[Jeff Griffiths (:canuckistani) (:⚡︎)]

You can, using the permissions property:

https://developer.mozilla.org/en-US/Add-ons/SDK/Tools/package_json#permissions

if this doesn't work for you, it's a bug. There is a separate argument wrt whether it should be the default.

Comment 2

[Tim Nguyen :ntim]

You still need a content script to do this. In the bug description, I mentioned : "without the hassle of using contentScripts inside the panels". I'm fine with setting permissions in package.json. But what I'm requesting is the ability to get cross-domain XHR from the panel script themselves.

Comment 3

[Jeff Griffiths (:canuckistani) (:⚡︎)]

(In reply to Tim Nguyen [:ntim] from comment #2)
> You still need a content script to do this. In the bug description, I
> mentioned : "without the hassle of using contentScripts inside the panels".
> I'm fine with setting permissions in package.json. But what I'm requesting
> is the ability to get cross-domain XHR from the panel script themselves.

I think the best way to approach panel development is to do as much scripting in content scripts as possible, for exactly this reason.

One of the issues is, it is difficult to separate remote panel content from 'local' panel content loaded from ./data, so we restrict any scripts in panel html code.