mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
93369747ec
This is just a heuristic, anyway, and some of the usage is downright broken.
There are two cases here:
1 - Deciding what to do for get{Own,}PropertyDescriptor. In these cases, we can
just enter with GET and rely on the filtering machinery to filter out dangerous
setters for security wrappers.
2 - Custom Xray props. None of these make sense in a |set| context. In fact,
they generally have null setters anyway, so we can just assume GET.
The policy-entering code in XrayWrapper is super haphazard. We'll get rid of it
entirely later in these patches.
|
||
|---|---|---|
| .. | ||
| AccessCheck.cpp | ||
| AccessCheck.h | ||
| ChromeObjectWrapper.cpp | ||
| ChromeObjectWrapper.h | ||
| FilteringWrapper.cpp | ||
| FilteringWrapper.h | ||
| Makefile.in | ||
| WaiveXrayWrapper.cpp | ||
| WaiveXrayWrapper.h | ||
| WrapperFactory.cpp | ||
| WrapperFactory.h | ||
| XrayWrapper.cpp | ||
| XrayWrapper.h | ||