Getting rid of the separate concepts of setters and creators

I'd like to propose that we get rid of the separate concepts of setters 
and creators [1].

In practice, only the following interfaces have a named or indexed 
setter as far as I can tell: DOMStringMap, HTMLOptionsCollection, 
HTMLSelectElement, Storage.  For all of these, the setter is also a creator.

Combining the concepts into the single concept of "setter" will make it 
simpler to actually specify the behavior for setting named properties, 
which is not web-compatible as currently specified.

Any objections?

-Boris

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=27988

Received on Tuesday, 10 February 2015 18:30:04 UTC