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

@TSMatthews, sorry for the delay... just coming back to this now: 

> Just to clarify on the addition of the new field (regionCode / region_iso_id) - is this now the field that will be mapped to from the 'region' dropdown on the UI (if there are regions for the country in question)? Want to be clear how both of these fields - 'region' and 'regionCode' would coexist and what we collect from the user.
 
 * `region` would be either what the browser presented to the user in the drop down, or whatever the user typed in (so, remains fairly unreliable... but might see convergence across browsers over time). 
 * `regionCode` would be the ISO 3166-2 code, or empty string when it can't be determined.
 
At least `regionCode` should help address most inconsistency issues you identified, with `region` serving as a fallback in the worst of cases.   

Could that work? 

-- 
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-360000039