Closed
Bug 1085071
Opened 10 years ago
Closed 10 years ago
Drop support for JSPropertyOp getters/setters in sandboxes
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
FIXED
mozilla36
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
We added this at some point, when we still had DOM stuff that was JSPropertyOp, but that hasn't been the case in a while.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8507485 -
Flags: review?(bobbyholley)
Comment 2•10 years ago
|
||
Comment on attachment 8507485 [details] [diff] [review]
Stop handling JSPropertyOp getters/setters in sandbox code, since we no longer have those around for any of the objects we care about
Review of attachment 8507485 [details] [diff] [review]:
-----------------------------------------------------------------
::: js/xpconnect/src/Sandbox.cpp
@@ +633,5 @@
> // Now fix up the getter/setter/value as needed to be bound to desc->obj.
> //
> // Don't mess with XPC_WN_Helper_GetProperty and XPC_WN_Helper_SetProperty,
> // because that could confuse our access to expandos.
> if (desc.getter() != XPC_WN_Helper_GetProperty &&
Can't we get rid of these two checks now, and the extern declarations above?
Attachment #8507485 -
Flags: review?(bobbyholley) → review+
Assignee | ||
Comment 3•10 years ago
|
||
> Can't we get rid of these two checks now, and the extern declarations above?
Looks like we can, now that window is not on XPConnect bindings. I'll do that.
Assignee | ||
Comment 4•10 years ago
|
||
Oh, and I verified that by running the manual test in bug 751077, and of course try.
Assignee | ||
Comment 5•10 years ago
|
||
Target Milestone: --- → mozilla36
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•