@adrianba said: > There will be no streamlining if you just present a list of arbitrary data fields. You might as well use a HTML form at that point. Only by applying semantic meaning to the data fields can the user agent be smart about how to populate them. Browsers do a pretty good job of this with form autocompletes today. I'd argue that the more granular data types (like email, address, phone number) will make this even easier. An alternative to solving this is to have a `requestGiftCardOrCouponNumber` member as an addition? But then I wonder what we would label this as it is probably different from merchant to merchant. The motivation for allowing this data collection directly by the user agent was originally for shipping address as it was argued that this could significantly streamline the checkout because almost all onine purchases include shipping. Now there is an argument to add email address and phone number and also define additional semantics about whether this data is required or optional but we are hearing directly from a company that services thousands of merchants: > who all have different data preferences or requirements for their customers to purchase something that trying to enumerate the set of data the user agent can collect is not going to work. So where do we draw the line and based on what logic? --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/pull/65#issuecomment-212888869
Received on Thursday, 21 April 2016 12:19:52 UTC