Make XPCNativeWrappers wrap and unwrap all values passed across the membrane

RESOLVED FIXED

Status

()

Core
JavaScript Engine
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: jorendorff, Assigned: jorendorff)

Tracking

Other Branch
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

7 years ago
So far XPCNWs haven't been terribly precise about this, because we're always calling into C++, which is going to unwrap everything anyway. Bug 563106 needs stronger guarantees which means being more precise.
(Assignee)

Updated

7 years ago
Blocks: 560643

Updated

7 years ago
Assignee: general → mrbkap
(Assignee)

Comment 1

7 years ago
Taking.
Assignee: mrbkap → jorendorff
(Assignee)

Comment 2

7 years ago
I think we plan to do this after bug 568671. Otherwise it's redundant work.

If that starts taking too long though I can do the redundant work, which isn't a whole lot, I think.
Depends on: 568671
(Assignee)

Updated

7 years ago
No longer blocks: 560643
(Assignee)

Comment 3

7 years ago
The XPCNativeWrapper re-implementation in js/src/xpconnect/wrappers takes care of this.  (It's called XrayWrapper<JSCrossCompartmentWrapper>.)

This is not exactly FIXED in the usual sense but I'm marking it RESO FIXED anyway because there's no point worrying further about it.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.