W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2011

Re: May the defineProperty method of a proxy handler throw a TypeError?

From: Mark S. Miller <erights@google.com>
Date: Wed, 10 Aug 2011 19:45:17 -0700
Message-ID: <CABHxS9j_5gnQUVZW3Qwexrjc+4Y5revwBbFkvSOtc5xC6e+QtQ@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: David Flanagan <dflanagan@mozilla.com>, Tom Van Cutsem <tomvc.be@gmail.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss <es-discuss@mozilla.org>
On Wed, Aug 10, 2011 at 7:20 PM, Cameron McCormack <cam@mcc.id.au> wrote:

> On 9/08/11 9:40 AM, Mark S. Miller wrote:
>
>> If there are no show-stopping legacy compat constraints forcing us to
>> specify Reject, I prefer that we specify these to throw a TypeError.
>>
>
> I can't say for sure, but I would be surprised if this didn't cause
> problems, given that it introduces exception throwing where currently
> assignment to non-writable properties of objects that need to be implemented
> as proxies (like NodeList) is just ignored.
>

Ok. If we decide not to, then I think it is important that proxies be able
to faithfully emulate ES5 failed "Reject" semantics, so that ES-next code
can fully implement a conformant DOM.

-- 
    Cheers,
    --MarkM
Received on Thursday, 11 August 2011 02:45:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:04 UTC