Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663)

@marcoscaceres Thank you.

'regionCode' does seem like it will help the inconsistency issues as it must be valid ISO3166-2.

Just so I am clear.. the forms could still have 'region' or 'regionCode' right? And it's really up to the browser vendors to implement it?

We would not have 'regionCode' being an expected field returned from every address form? 'regionCode' solves inconsistency of value issues, but if it's not a mandatory field, it won't fix our issue that we always need this value (original post -> need region as consistent data and always present, so that we can verify against shipping rules / options specific to certain regions).

-- 
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/663#issuecomment-360781989