W3C home > Mailing lists > Public > public-payments-wg@w3.org > January 2016

Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)

From: Manu Sporny <notifications@github.com>
Date: Thu, 21 Jan 2016 08:28:50 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/39/173624889@github.com>
> In time this will be deprecated in favor of more generic APIs like those being worked on by the VCTF.

Do not build cruft into the Web Platform. The API call will /never/ be deprecated or removed from the browser because websites will start to depend on it. If we are going to do this, we must make a best effort to get it right. APIs for the Web Platform aren't like a software libraries - you can't deprecate them.

-1 to the counter-proposal that builds cruft into the Web Platform.

Reply to this email directly or view it on GitHub:
Received on Thursday, 21 January 2016 16:29:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:13 UTC