Form filling and custom fields

off-road-biker

<div class="IPBDescription">international forms, etc.</div>Hi,



since the beginning 1password has problems to fill the street, No. of the house etc - means german adresses in forms.

I always have to fill out the forms by typing cause 1password just fills a few lines. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/sad.gif' class='bbc_emoticon' alt=':(' />



And it also fills my first AND surename in the surename field - but in 1password there's just the surename.

Also instead of my birthday it fills my mailadress or the birthday in wrong style (not 12.06.1971 but Tuesday, 12.06.1971)

Or instead of telefon number my mail.



[size="5"][b]Please help![/b][/size]





Here are some links for a german form:

https://www.dew21.de/de/Privat--und-Gewerbekunden/Kontakt/Kontaktformulare.htm

http://www.polo-motorrad.de/de/contacts

http://www.louis.de/_1058b47035402d252ad007cc70908f08c3/index.php?topic=kontakt_louismail&menu_context=service

http://www.energy.de/news/lesen/article/queensland/

https://aktionen.postbank.de/api/;jsessionid=Ycq0tZjSERErmvIy43E+jg__.node11?x=UnzFhQpAUjlbjNoTjEAj*A



And the pic how it fills the fields:

khad

Hallo off-road-biker,



Es tut mir leid für die Mühe. There are a couple different problems that come into play in these situations.



1Password is developed in English, and so, while we have localized versions of the application, the localized text is only in the user interface. The code itself is not "localized." This can lead to some confusion regarding how 1Password works.



1Password fills information based on the underlying field names in the code on each website. For example, if there is a form field that has the word "Straße" next to it, the actual name of the input field to which that text refers may be called "street," "strasse," or "geschmacksache." Each website has complete control over what they name their fields. 1Password [b]is[/b] smart enough to deal with [b]multi-lingual[/b] variations of common field names for addresses, phone numbers, and the other information used in [url="http://help.agilebits.com/1Password3/3min_1fill.html"]Identity filling[/url], but it is not comprehensive.



We certainly have our work cut out for us if we try to guess what the trillions of websites on the Internet are going to be naming their fields (in the thousands of languages spoken all over the world). Thankfully, there is a standard!



Now, the tricky thing about HTML, CSS, and other web standards is that they are not mandatory. People just agree, "This is a good way to do this, and if we all do it this way everything will work together better." The [url="http://tools.ietf.org/html/rfc4112"]Electronic Commerce Modeling Language (ECML), Version 2 Specification[/url] is such a standard. When websites follow this international standard when [i]creating[/i] forms, 1Password fills in the forms quite well because 1Password also follows the ECML standard for [i]filling[/i] forms. Beautiful harmony. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



Unfortunately, not all websites follow this standard, and we end up back where we started: a seemingly impossible task of keeping track of the form fields used on all the websites in all the languages in the world.



I certainly can't guarantee that it will make a difference, but you might try contacting the owners of the websites where you are having these problems and point them to the ECML specification. Many web developers are not aware of the specification and are happy to make the simple changes to the code of their forms. As a bonus, this can also provide better interoperability for disabled users who rely on assistive technology. Everybody wins!



We have had some very conscientious [url="http://forum.agile.ws/index.php?/topic/3380-making-input-fields-compatible-with-1password/"]web developers ask us how to make their websites compatible with 1Password[/url]. I am always pleased when I can point them to an international standard which benefits everyone rather than something we just made up that only benefits 1Password users.



With that said, we're excited to tackle this very difficult problem, and form filling is something that we are constantly working to improve (even if some web developers are not so conscientious). Future updates of 1Password will increase the accuracy of the form filler for both credit cards and identities.



I hope that helps. Please let me know.



Mit freundlichen Grüßen

chadseld

Hi off-road-biker,



I have added these websites to our list of sites to test. As we improve the filling algorithm in the future, these sites will be tested regularly. Thank you for reporting these problems.

Zarkov

When I use the wallet function to fill in credit card information, sometimes 1PW does not recognize the cryptic names assigned by the vendor to the text fields, and hence will not fill them with the correct information. For example, my propane supplier has the credit card field named "txtCardNo" and the security code field "txtCin". (I identified these by using the x-Ray add-in to Safari). It would be really cool if we could manually add aliases to the default field names so these often-used credit card fields would be filled out.



Or is this already possible, and I just don't know how to do it?

khad

Hello Zarkov,



I merged your post with this existing thread as I think it gives some important background information. Please see my post above for some details on the form filling process.



With all of that said, I would love to get a look at the sites where you are having trouble, and customizable fields is an interesting suggestion. I will pass that along to the developers.