mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
011c97a205
I'm adding asserts about when we do and don't have a Location object behind the wrapper, and this case was hitting them. What we do here doesn't so much matter given how this stuff all works. On the one hand, statically using a restrictive policy is slightly more defense-in-depth. On the other hand, if this stuff is broken we're screwed in much more serious ways than content reading chrome locations, and using a consistent wrapper scheme allows us to make stronger asserts and assumptions. I opted for stronger assumptions and more understandable security code. If Blake feels strongly though, I could go the other way and sprinkle '|| isChrome(obj)' throughout the asserts though. |
||
|---|---|---|
| .. | ||
| AccessCheck.cpp | ||
| AccessCheck.h | ||
| CrossOriginWrapper.cpp | ||
| CrossOriginWrapper.h | ||
| FilteringWrapper.cpp | ||
| FilteringWrapper.h | ||
| Makefile.in | ||
| WrapperFactory.cpp | ||
| WrapperFactory.h | ||
| XrayWrapper.cpp | ||
| XrayWrapper.h | ||