[whatwg] Proposal:Improve internationalization in the autocomplete attribute

[Albert Bodenhamer]

Lara Rennie (CCed) and I have been looking over the autocomplete
attribute<http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#attr-fe-autocomplete>over
the past week with an eye towards better i18n.  We'd like to propose a
few changes.

Some are covered in https://www.w3.org/Bugs/Public/show_bug.cgi?id=22286.
 The rest I'll address here.

Address lines:
Currently: Recommended handling for addresses is currently as a single
line.  Alternatively, sites can ask for address lines 1-3 but this is
discouraged.
Problem: Single line doesn't work well for all regions. Some areas have 5
lines for an address and might have more.
Proposal: If address is requested as a single line newlines should be
preserved when filling. Stop discouraging the use of address-lines. Support
more than 3 lines for address.  Potentially, address-lineX where X can be
1-9.

Address 'locality':
Problem: Some regions have the concept of a "post town".  It's currently
unclear how this should be requested.
Proposal: Add "post town" to the list of expected localities in the
description to make it more clear how this should be requested.

Address CEDEX codes:
Problem: They don't fit well into the "postal-code" field and are often
handled as a separate entity.
Proposal: Add a field name for CEDEX code.

Address: Physical vs mailing address
Problem: It might be desirable to be able to specify that a physical
address (an actual location) is expected rather than a mailing address (eg
a PO box).
Proposal: Open to suggestions.

Phone:
Problem: The detail sections for phone number are very US-centric.  The
spec discourages the use of the detail sections as a result, but sites may
want to get phone number broken into chunks.
Proposal: Consider adding additional detail sections to reduce the US bias.

Thanks.

-- 
Albert Bodenhamer | Software Engineer | abodenha at chromium.<abodenha at google.com>
org