Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100)

> For indexed getters/setters, things are complicated, not least because there are legitimate use cases that have no other solutions right now. Indexed setters do require some careful spec prose around out-of-bounds sets.

Thanks.  This case is indexed getters / setters only.

> I think there is a large camp that considers some of the API goals of Typed OM as currently specified to be broken by design. Not the actual functionality, but the use of typing and typechecking. I personally am not in this camp, so I do not want to speak for it, but just wanted to mention its existence. This is part of the issue you are encountering with pushback on the Typed OM use of indexed getters/setters.

Thanks for the heads up.  Can you point to anywhere that this feedback has been given publicly?  I didn't come across it when [scanning the open issues](https://github.com/w3c/css-houdini-drafts/issues?q=is%3Aissue+is%3Aopen+label%3Acss-typed-om-1) or [initial TAG feedback](https://github.com/w3ctag/design-reviews/issues/223), but I only did a quick scan so I may have missed it.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/100#issuecomment-365658355