- From: Julien Cayzac <notifications@github.com>
- Date: Mon, 19 Oct 2020 03:20:18 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 19 October 2020 10:20:30 UTC
Yeah… In the context of a PWA using the Payment Handler API, the address input may rely on web forms annotated with `autocomplete=address-level3` etc… Now, I am assuming that the reasoning behind fixing semantics in `PaymentAddress` is that since it is being consumed by a merchant it should not depend on the locale of either the end-user nor that of the payment handler, which kind of makes sense. So, it's up to the payment handler to "standardize" the address and produce a locale-invariant address. (That the Contact Picker API reuses `PaymentAddress`, OTOH, really doesn't make much sense to me to be honest. But I guess that's an issue for another working group 😉 ) -- 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/payment-request/issues/932#issuecomment-711991884
Received on Monday, 19 October 2020 10:20:30 UTC