<E202D2AE-2994-4993-ACBA-A52B02A62048@gmail.com>
Current votes: None.
...as I'm in the middle of a project implementing schema.org markup, is ther= e any consideration of using those properties as the tokens within the autoc= omplete attribute? While not perfectly compatible, it would lessen the burden on developers=E2=80= =94"Is it given-name or givenName for form fields?"=E2=80=94and schema.org's= notion of scoping might prove a better solution than the section- nomenclat= ure. After all, form elements already have a grouping element in <fieldset>.= In any case, I echo Jon's sentiment: looking forward to it! =E2=80=94 nz On Feb 15, 2012, at 4:10 PM, Jon Honeycutt <jhoneycutt@apple.com> wrote: > I've shown this proposal to a couple of people here at Apple, and we have n= o issues with it. I'm personally eager to see it move forward! >=20 > -- > Jon >=20 > On Dec 15, 2011, at 1:17 PM, Ilya Sherman <isherman@chromium.org> wrote: >=20 >> Current autofill products rely on contextual clues to determine the type o= f data that should be filled into form elements. Examples of these contextua= l clues include the name of the input element, the text surrounding it, and p= laceholder text. >>=20 >> We have discussed the shortcomings of these ad hoc approaches with develo= pers of several autofill products, and all have been interested in a solutio= n that would let website authors classify their form fields themselves. Whil= e current methods of field classification work in general, for many cases th= ey are unreliable or ambiguous due to the many variations and conventions us= ed by web developers when creating their forms: >>=20 >> + Ambiguity: Fields named "name" can mean a variety of things, including= given name, surname, full name, username, or others. Similar confusion can o= ccur among other fields, such as email address and street address. >>=20 >> + Internationalization: Recognizing field names and context clues for al= l the world=E2=80=99s languages is impractical, time-intensive, and error-pr= one (as good context clues in one language may mean something else in anothe= r language) >>=20 >> + Unrelated Naming: Due to backend requirements (such as a framework tha= t a developer is working within), developers may be constrained in what they= can name their fields. As such, the name of a field may be unrelated from t= he data it contains. >>=20 >>=20 >> We believe that website authors have strong incentive to facilitate autof= ill on their forms to help convert users in purchase and registration flows.= Additionally, this assists users by streamlining their experience.=20 >>=20 >> To that end we would like to propose adding an autocompletetype attribute= [1] to the HTML5 specification, as a complement to the existing autocomplet= e attribute that would eliminate ambiguity from the process of determining i= nput data types. We developed this initial draft proposal working together w= ith developers or several autofill products, and are now looking forward to f= eedback and suggestions from the broader community. >> [1] http://wiki.whatwg.org/wiki/Autocompletetype >>=20 >> Thanks, >> ~Ilya Sherman, Chromium Autofill Developer >=20