\n common profile information and pre-populating the form with those values. Unfortunately, up to
\n now it has been difficult for webmasters to ensure that Chrome and other form-filling providers
\n can parse their form correctly. Some
\n standards exist<\/a>;
\n but they put onerous burdens on the implementation of the website, so they’re not used much in
\n practice.\n<\/p>\n
\n Today we’re pleased to announce support in Chrome for an experimental new “autocomplete type” \n Just add an attribute to the input element, for example an email address field might look like:\n<\/p>\n \n We’ve been working on this design in collaboration with several other autofill vendors. Like any \n For more information, you can read the Wednesday, January 25, 2012 One of the biggest bottlenecks on any conversion funnel is filling out an online form \u2013 shopping and registration flows all rely on forms as a crucial and demanding step in accomplishing the goals of your site. For many users, online forms mean repeatedly typing common information like our names and […]<\/p>\n","protected":false},"menu_order":84636,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24646","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24646","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24646\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/26918"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24646"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24646"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24646"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n attribute for form fields that allows web developers to unambiguously label text<\/code>
\n and select<\/code> fields with common data types such as ‘full-name’ or ‘street-address’.
\n With this attribute, web developers can drive conversions on their sites by marking their forms
\n for auto-completion without changing the user interface or the backend.\n<\/p>\n![\"How](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-73ce97abe305.png\")
<\/p>\n
\n early stage proposal we expect this will change and evolve as the web standards community provides
\n feedback, but we believe this will serve as a good starting point for the discussion on how to
\n best support autofillable forms in the HTML5 spec. For now, this new attribute is implemented in
\n Chrome as x-autocompletetype<\/code> to indicate that this is still experimental and not yet
\n a standard, similar to the webkitspeech<\/code> attribute we
\n released<\/a>
\n last summer.\n<\/p>\n
\n full text of the proposed specification<\/a>,
\n ask questions on the
\n Webmaster help forum<\/a>,
\n or you can share your feedback in the
\n standardization discussion<\/a>!\n<\/p>\n