On Mon, Oct 12, 2015 at 6:43 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: > You don't even need to do that. You just return WindowProxy or Window or > whatever, and Location. The cases when you need to return a cross-origin > thing will only happen via cross-origin access of some sort, so that's the > place where you'll define wrapping in the cross-origin thing...
What does that mean, concretely? > I guess the main issue there is .contentWindow, right? That's the one place > where the cross-origin access is implicit... Yeah, that and self[0], which is defined as an indexed getter that returns a WindowProxy at the moment. > Oh, and it's not quite clear to me what happens when you have a > used-to-be-same-origin WindowProxy become cross-origin on navigation. I > assumes that's defined somewhere in the relevant spec bit... That's defined? https://old.etherpad-mozilla.org/html5-cross-origin-objects does not mention it. -- https://annevankesteren.nl/
