W3C home > Mailing lists > Public > www-archive@w3.org > October 2015

Re: Defining exotic objects in IDL, HTML, or both?

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 13 Oct 2015 08:31:51 +0200
Message-ID: <CADnb78iry89+MT5JHCiXpKLDv8OyL9zZe0xhcehGKwE-PV8yaQ@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Domenic Denicola <d@domenic.me>, Cameron McCormack <cam@mcc.id.au>, www-archive <www-archive@w3.org>
On Mon, Oct 12, 2015 at 6:43 PM, Boris Zbarsky <bzbarsky@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.

Received on Tuesday, 13 October 2015 06:32:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:35:26 UTC