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 04:22:25 +0000
To: public-script-coord@w3.org
Message-ID: <bug-22320-3890-tuL4J8Gsm5@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22320

--- Comment #9 from Boris Zbarsky <bzbarsky@mit.edu> ---
Mark, at the same time implementations already don't return them from
getOwnPropertyNames.  Furthermore, defining getOwnPropertyNames to return them
requires an ordering to be put on the property names, and the current ordering
defined in the specification is ... somewhat insane to actually implement. 

Futhermore, last I checked it's not hard to create objects in ES6 that have
that behavior for getOwnPropertyNames: just have a direct proxy return [] from
the relevant trap.

I think we can all agree that objects like this one (with random named
properties that come and go) are perverse, unexpected, hostile to the
JavaScript programmer, and likely in violation of the ES5 spec.  The only
reason they exist is backwards-compat, and I would argue that we should define
them in the simplest possible way that's needed for said backwards compat and
stop wasting time on them...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 9 July 2013 04:22:27 UTC

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