Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100) from Rick Byers on 2018-02-14 (public-webapps-github@w3.org from February 2018)

From: Rick Byers <notifications@github.com>
Date: Wed, 14 Feb 2018 13:29:47 +0000 (UTC)
To: heycam/webidl <webidl@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <heycam/webidl/issues/100/365606973@github.com>

Is it really true that getter/setter is "legacy" and discouraged in new APIs?  Can anyone provide a reference for this documenting the extent of the consensus here?  In the absence of agreed upon guidance (eg. captured concretely in the webidl spec), I'm personally not willing to block requests to ship such new APIs in blink (such as [Typed OM](https://groups.google.com/a/chromium.org/d/msg/blink-dev/6ai8np0DSOA/XJak-Nw0AgAJ)).

/cc @ajklein @foolip @chrishtr

-- 
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-365606973

Received on Wednesday, 14 February 2018 13:30:15 UTC