Closed Bug 525249 Opened 15 years ago Closed 6 years ago

XPCNativeWrapper should have second optional parameter to allow for cross-origin use

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INACTIVE

People

(Reporter: avarma, Unassigned)

Details

(Whiteboard: [jetpack]) 

Jetpacks need to be able to access XPCNativeWrapped DOM elements and such from principals other than that of the jetpack itself; for instance, a jetpack from foo.com, if it's given permission to access google.com and twitter.com, should be able to interact with browser tabs containing pages belonging to those domains in much the same way that a standard Firefox extension can.

The difference between Firefox extensions and Jetpacks, however, is that the former run with the system principal, while the latter run with content principal. So it'd be very helpful to be able to specify e.g. a second parameter of type nsIPrncipal that allows the XPCNativeWrapped object to be accessed from that principal (this is much like bug 524771, only for XPCNativeWrappers instead of XPCSafeJSObjectWrappers).
Summary: [jetpack]: XPCNativeWrapper should have second optional parameter to allow for cross-origin use → XPCNativeWrapper should have second optional parameter to allow for cross-origin use
Whiteboard: [jetpack]
Blocks: 543856
You say it would be very helpful, but is this a blocker for Jetpack?
No longer blocks: 543856
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.