Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties from Mark Miller on 2014-12-01 (public-script-coord@w3.org from October to December 2014)

From: Mark Miller <erights@gmail.com>
Date: Sun, 30 Nov 2014 19:29:08 -0800
To: "Mark S. Miller" <erights@google.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss <es-discuss@mozilla.org>
Message-ID: <CAK5yZYhXBebxR7mjvLeHT7EpjeiMyUahByFLQuCYNcDhkmbJrQ@mail.gmail.com>

On Sun, Nov 30, 2014 at 6:12 PM, Mark S. Miller <erights@google.com> wrote:
[...]
> Put another way, if this invariant is preserved by WindowProxy, then

Should be: "is not preserved by" or "is violated by"

> anyone else seeking to create another object that violates this
> invariant can create a Proxy whose target is a WindowProxy. Its
> violation enables further violations. The invariants are inductive. A
> violation breaks the induction.


-- 

  Cheers,
  --MarkM

Received on Monday, 1 December 2014 03:29:35 UTC