W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

Re: WebIDL and prototype chains

From: Adam Barth <w3c@adambarth.com>
Date: Thu, 16 Jul 2009 15:21:03 -0700
Message-ID: <7789133a0907161521vc3eed2fu4c3a42bf3a820693@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Maciej Stachowiak <mjs@apple.com>, public-webapps <public-webapps@w3.org>
On Thu, Jul 16, 2009 at 3:08 PM, Jonas Sicking<jonas@sicking.cc> wrote:
> On Thu, Jul 16, 2009 at 2:59 PM, Maciej Stachowiak<mjs@apple.com> wrote:
>> One thing to note: any object or method that is exposed cross-origin should
>> specifically *not* have this behavior. Instead, it should create a separate
>> interface object in every frame that accesses the property. window.history,
>> window.location and window.postMessage are examples that require this
>> treatment. Web IDL needs to give a hook to other specs so they can specify
>> that cross-origin properties need to get this different treatment.
> I definitely agree you definitely don't want the inner windows
> prototype values if it's a cross-origin window. What you should get is
> less clear to me.
> If you should get the outer windows prototype or some sort of blank
> prototype. Personally it'd make the most sense to me if you got a
> blank prototype since that seems like the most consistent behavior.

Either behavior seems fine to me.  I'd just like to see it speced
somewhere so we can all do the same thing.  :)

Received on Thursday, 16 July 2009 22:22:05 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:17 UTC