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

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

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Mon, 12 Oct 2015 12:43:29 -0400
To: Domenic Denicola <d@domenic.me>, Anne van Kesteren <annevk@annevk.nl>
Cc: Cameron McCormack <cam@mcc.id.au>, www-archive <www-archive@w3.org>
Message-ID: <561BE331.9070301@mit.edu>
On 10/12/15 12:11 PM, Domenic Denicola wrote:
> Since these are only used as return types and not as arguments, just using `object` or `any` would work, since return types in IDL are just documentation anyway.

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...

I guess the main issue there is .contentWindow, right?  That's the one 
place where the cross-origin access is implicit...

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...

-Boris
Received on Monday, 12 October 2015 16:44:01 UTC

This archive was generated by hypermail 2.3.1 : Monday, 12 October 2015 16:44:01 UTC