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

--- Comment #18 from Mark S. Miller <erights@gmail.com> ---
(In reply to comment #17)
> > the ES specs do not specify any particular order for this.
> 
> One of the goals of the current web specs is to not have undefined behavior.
> That means they do in fact specify an order here.

Other things being equal, removing undefined behavior from specs is a great
thing. I've fought for this many times in tc39 as well. However, breaking a
feature because
1) the feature itself could be provided cheaply, in a way that conforms to the
es spec, at the price of non-deterministic order.
2) the defined order, which no one really cares about for this feature, would
for some reason be expensive.

Btw, why would a deterministic order for this be expensive? I don't get it.


> Again, if the spec changes such that it's sane to implement, it'll perhaps
> get implemented (I obviously can't speak for WebKit or Blink, but we would
> implement in Gecko).  If it does not, it probably won't be (as now).

So how about we change the spec to "have getOwnPropertyNames return a list of
the own property names"? What is the right forum to get this spec changed?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 9 July 2013 17:16:05 UTC

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