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: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Thu, 15 Jan 2015 02:56:30 +0100
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Ian Hickson <ian@hixie.ch>, "Mark S. Miller" <erights@google.com>, Travis Leithead <travis.leithead@microsoft.com>, Domenic Denicola <domenic@domenicdenicola.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss <es-discuss@mozilla.org>
Message-ID: <7v6eba1sd8p01f0qu1av1as3il8e7nf793@hive.bjoern.hoehrmann.de>
* Boris Zbarsky wrote:
>You say "every WindowProxy", but in practice in an ES implementation you 
>have some object, it has some internal methods.  This is the last time 
>I'm bothering to go through this with you, since clearly we're getting 
>nowhere, as I said in https://www.w3.org/Bugs/Public/show_bug.cgi?id=27128

What are the odds that the behavior observable by web pages can actually
be defined sanely such that ES invariants and compatibility requirements
are satisfied? https://www.w3.org/Bugs/Public/show_bug.cgi?id=27128#c15
indicates, as I understand it, the odds may be quite good. In that case,
looking for a volunteer to come up with a proposal might be a good next
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
D-10243 Berlin · PGP Pub. KeyID: 0xA4357E78 · http://www.bjoernsworld.de
 Available for hire in Berlin (early 2015)  · http://www.websitedev.de/ 
Received on Thursday, 15 January 2015 01:57:21 UTC

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