mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
f99be51d16
I did this wrong before. Making this a SecurityWrapper means that the caller does not subsumes the target, and that the target therefore needs to be protected from the caller. But GentlyOpaque was supposed to be an analog of PermissiveXray for use when no useful XrayTraits exist, so it should behave similarly. If we make this a Filtering Security Wrapper, we get a bunch of assertions where we expect CheckedUnwrap to succeed for a chrome-side wrapper. And we can't making it a Filtering Non-Security Wrapper, because then the filtering policy isn't even consulted (an optimization in jsproxy.cpp). Really, we want all of the Xray machinery (like the ability to waive and to place expandos), and we just don't want to resolve any properties. This patch does this. |
||
|---|---|---|
| .. | ||
| ductwork/debugger | ||
| examples | ||
| ipc | ||
| public | ||
| src | ||
| xpconnect | ||