On 1/29/15 4:36 PM, Yehuda Katz wrote:
> Are you asking what to do about the fact that existing WebIDL "classes"
> produce enumerable properties that probably can't be made non-enumerable
> without breaking the web?

I think the following things need to be decided:

1)  What should the behavior be for WebIDL objects going forward?
2)  If the going forward behavior is to have properties non-enumerable,
     should we try to migrate some subset of the existing Web IDL
     objects to the new behavior?

I'm pretty sure we can't migrate all existing things, at least without 
breaking someone somewhere, but I suspect we can migrate many of them, 
if we decide it's actually worthwhile.

I'd be pretty interested in knowing what other implemntors think here, 
because if we make some decision on #1 I'd rather not have people 
continue to ship whatever they do now instead of what we decided on. 
We've been having a _lot_ of that happen with Web IDL.  :(

-Boris

I think the following things need to be decided:

1.  What should the behavior be for WebIDL objects going forward?
2.  If the going forward behavior is to have properties non-enumerable,
     should we try to migrate some subset of the existing Web IDL
     objects to the new behavior?

I'm pretty sure we can't migrate all existing things, at least without 
breaking someone somewhere, but I suspect we can migrate many of them, 
if we decide it's actually worthwhile.

I'd be pretty interested in knowing what other implemntors think here, 
because if we make some decision on #1 I'd rather not have people 
continue to ship whatever they do now instead of what we decided on. 
We've been having a _lot_ of that happen with Web IDL.  :(