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

>> @mnoorenberghe,
>> 
>>     libaddressinput doesn't currently have regions for Belgium and indicates that they're not required for mailing labels so it's easiest for us to pretend they don't exist but I'm trying to get this understanding standardized as I don't want some browsers returning regions for Belgium and others not.
@marcoscaceres 
> I don't know if we can standardize that behavior. That seems overly prescriptive and would be too closely tied to libaddressinput (which neither Edge or Safari rely on).

Sorry, just noticed this reply now…

What I'm talking about isn't tied to libaddressinput at all. It's tied to whether the country writes subdivisions as part of their mailing address (e.g. on an envelope). Since users won't expect to be asked to select their subdivision for a shipping address in some countries that don't use them for mailing, I expect that in Firefox we won't show a subdivision field and therefore won't populate the region or regionCode fields for those countries such as Belgium, Germany, etc. Perhaps the spec and/or MDN should be more clear that an empty string can be valid for mailing purposes.

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