On 5/15/14, 8:21 AM, Ehsan Akhgari wrote:> On 2014-05-15, 5:29 AM, Anne van Kesteren wrote:
>> On Wed, May 14, 2014 at 1:52 AM, Brian Nicholson
>> <bnichol...@mozilla.com> wrote:
>>> If we disagree with this proposal:
>>>
>>> What alternatives do we have? Given that countries require more than
>>> two administrative levels in postal address, it seems our options are
>>> limited. We can't simply provide a single blob for an entire address
>>> as sites generally require more tokenized information.
>>
>> You do not want to tie this to a particular localization. E.g. I use
>> the en-US version of Firefox, but I make payments with European credit
>> cards. Localization should not affect functionality.
>
> Yes, this should definitely be tied to the locale of the page not the UA.

If you're referring to which fields to show in the requestAutocomplete (rAc) UI, the ideal plan IMO would be to tie it to the country the user chooses in their autocomplete profile in the browser. So if I choose China as the country, I will see the three (or soon four) levels of address fields required, whereas choosing USA will only have City and State. The field labels would be in the language of the UA but would be localized for the country chosen.

> Do you know if Chromium or any other projects have an open source
> version of this mapping that we can use at least as a baseline?

If you are referring to the localized names for all of the level fields in each region, then I don't know about such a mapping but I haven't looked for one.

I believe Chromium is planning on using libaddressinput (that Brian linked to) in order to know which fields are required and the proper order. Unfortunately it only supports two address levels at the moment though.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to