Re: WindowProxy as the key in ES6 Set/Map/WeakSet/WeakMap from Adam Barth on 2014-04-16 (public-script-coord@w3.org from April to June 2014)

From: Adam Barth <abarth@chromium.org>
Date: Wed, 16 Apr 2014 07:30:06 -0700
To: Domenic Denicola <domenic@domenicdenicola.com>
Cc: "Mark S. Miller" <erights@google.com>, Toon Verwaest <verwaest@chromium.org>, Rick Waldron <waldron.rick@gmail.com>, Boris Zbarsky <bzbarsky@mit.edu>, Adam Klein <adamk@chromium.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <CAP=28cdXMUzpLZff3h14y-rj8TkjNs=+MmUpo6RSx6fB_tZR+g@mail.gmail.com>

On Wed, Apr 16, 2014 at 7:25 AM, Domenic Denicola <
domenic@domenicdenicola.com> wrote:

> On Apr 16, 2014, at 10:14, "Adam Barth" <abarth@chromium.org> wrote:
> > I don't believe there's an experiment you can run today in browsers to
> answer that question.  Map would give you a way to answer that question,
> which is why we need to decide what the answer ought to be.
>
> Map is entirely implementable in today's JavaScript, modulo efficiency
> concerns. So I don't see how this could be true. The answer should be
> whatever such a JS Map implementation does.
>

Hum...  In that case, I think we need to act as if the identity of the
WindowProxy is preserved across browsing context navigations.

Adam

Received on Wednesday, 16 April 2014 14:31:03 UTC