[Bug 26985] Remove requirement for prose around iterable<> if object has indexed properties

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26985

--- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> ---
That said, I looked more carefully at web idl today and it looks like the
current behavior is in fact well-defined in that:

1)  If you have an indexed getter and iterable<> then your value set is your
indexed values (this is defined in the non-ES-specific section of the spec).

2)  The ES section makes this work by requiring the use of something other than
the Array iterator in this case.

I think #2 is a bug we should fix, but #1 means there is in fact no need for
prose defining the value set when setting iterable<> on an interface with
indexed props

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Monday, 6 October 2014 12:29:55 UTC