- From: <bugzilla@jessica.w3.org>
- Date: Tue, 09 Jul 2013 04:22:25 +0000
- To: public-script-coord@w3.org
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