W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2015

Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties

From: Yehuda Katz <wycats@gmail.com>
Date: Thu, 15 Jan 2015 03:19:27 +0000
Message-ID: <CAMFeDTX93m_YJ73mbj4JFuXbZgS+YuUGg2YwOmpapbiZyQxVug@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>, Boris Zbarsky <bzbarsky@mit.edu>
Cc: es-discuss <es-discuss@mozilla.org>, "Mark S. Miller" <erights@google.com>, Domenic Denicola <domenic@domenicdenicola.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Travis Leithead <travis.leithead@microsoft.com>
bz said:

> ES also allows other "exotic objects" that define some other behavior
> for those internal methods, but requires that the invariants be
> preserved.

Hixie said:

So one option would be to just say that WindowProxy is not an ES object.


If it's available to JavaScript consumers it must look like an object that
obeys ES invariants to JavaScript consumers. No (new, ugh) exceptions.
Received on Thursday, 15 January 2015 03:19:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC