Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1)

@adrianhopebailie,

>  Using a list of tokens means the API spec does not need to change in future for new types to be added.

I don't think I agree. If you want to change what it means to conform (by adding a new feature) you need to revise the spec.

So I think the difference is only syntactic. I happen to like the list of tokens, but want to know whether that's a pattern that is preferable for JS developers.

> I believe that we should approach the conformance around this functionality as a "best effort". In other words some browsers will be able to gather some data and others won't but we shouldn't have a hard-coded list that they MUST define UI for.

If we take that approach, it will be (even more) important for user agents to declare programatically what features they support.

> If the payment request should not be passed to the payment app at all without the data having been captured then we need to handle that case too.

Related: issue 97
 https://github.com/w3c/browser-payment-api/issues/97

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/1#issuecomment-208450411