Re: [w3c/browser-payment-api] Why another API? (#203)

@tjconcept,

> I fear this is putting unnecessary responsibilities on browsers and browser vendors (which is never good) unless some basic functionality is needed that is not currently available to web applications.

I believe that browser vendors are particularly interested in this work (judging by who has joined the Working Group). And, as I mentioned, the behavior we are working on is not currently standardized on the Web, so it is not currently available to Web applications.

> And then I would rather have vendors focus on those fundamentals. Like for instance better inter communications.

Do you mean "fundamentals for payments"? What are the fundamentals you have in mind?

Of course, there's a lot of work going on at W3C (and elsewhere) to expand Web technology capabilities; this is just one effort. Browser vendors themselves prioritize what they are going to implement for their customers.

Ian





---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/203#issuecomment-220799747