Closed
Bug 599604
Opened 14 years ago
Closed 14 years ago
Implement LocationWrapper
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jorendorff, Assigned: gal)
References
Details
Attachments
(1 file, 2 obsolete files)
|
9.51 KB,
patch
|
Details | Diff | Splinter Review |
In xpcconvert.cpp, in NativeInterface2JSObject, where we currently call ClassNeedsXOW, the new code will still need to do something special for the Location object.
This requires a slightly custom wrapper (but mostly just like a XOW).
|
Reporter | |
Updated•14 years ago
|
Blocks: compartments
|
|
Reporter | |
Comment 1•14 years ago
|
||
With this patch, AccessCheck::isLocationObjectSameOrigin asks the SecurityManager for the Location object's object principal. That's what we currently do, I think, but it's not what we want to do long-term.
Is there already a way to ask a Location object what compartment or
inner window the outer window is currently navigated to? If not, can I add a
non-scriptable method on nsIDOMLocation?
Attachment #478525 -
Flags: feedback?(mrbkap)
|
Assignee | |
Comment 2•14 years ago
|
||
Assignee: jorendorff → gal
Attachment #478525 -
Attachment is obsolete: true
Attachment #478525 -
Flags: feedback?(mrbkap)
|
|
Assignee | |
Comment 3•14 years ago
|
||
Attachment #479276 -
Attachment is obsolete: true
|
||
Comment 4•14 years ago
|
||
This is in the queue now.
|
|
Reporter | |
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•