- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 10 Feb 2015 19:48:22 +0100
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: "public-script-coord@w3.org" <public-script-coord@w3.org>
On Tue, Feb 10, 2015 at 7:29 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > I'd like to propose that we get rid of the separate concepts of setters and > creators. > > 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? Seems fine to me. Note that there's also the proposal to label these legacy* to encourage writing classes that don't require proxies. -- https://annevankesteren.nl/
Received on Tuesday, 10 February 2015 18:48:48 UTC