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

[Bug 22320] Form's supported property names should perhaps not be enumerable

From: <bugzilla@jessica.w3.org>
Date: Tue, 09 Jul 2013 23:08:27 +0000
To: public-script-coord@w3.org
Message-ID: <bug-22320-3890-mG2VqCo9Ey@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22320

--- Comment #32 from Mark S. Miller <erights@gmail.com> ---
(In reply to comment #31)
> > There is no explicit mention in the WebIDL spec of them behaving in interesting > ways with those.
> 
> Just to be clear, this was wrong.  seal/freeze/preventExtensions throw on
> things with named or indexed props.

In that case, you are correct that ES allows the object to claim not to have
own properties (e.g., via getOwnProperties returning an empty list) and then
later claim to have properties (e.g., via getOwnPropertyDescriptor).

Nevertheless, we all seem to agree at this point that this behavior is
programmer hostile and there's nothing that prevents us from fixing it. From
Ian's comments, only WebIDL needs to be fixed -- the HTML spec is neutral on
the matter.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 9 July 2013 23:08:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC