News for hackers. Stuff that matters.
Re:Chrome’s requestAutocomplete() by r00fus on Thursday May 16, 2013 @01:32PM (#5719793)
The main issue I have with autocomplete is that the data can vary by site - which means stale data is possible.

I don't use autocomplete, I use 1password, which guarantees my information is as up to date as I want it to be for all sites.

Perhaps browser extensions like 1Password can also leverage this to keep your autocomplete data up to date with your main contact/credit details?

Re:Chrome’s requestAutocomplete() by sharth on Thursday May 16, 2013 @01:36PM (#5719814)
The initial implementation appears to be targeted to e-commerce sites. Your username and password are not included in the fields that this can populate.

Here are the supported fields:

* Contact: name, tel, email

* Shipping: street-address, address-line1, address-line2, locality, region, country, postal-code

* Billing: street-address, address-line1, address-line2, locality, region, country, postal-code

* Payment: cc-name, cc-number, cc-exp, cc-csc, cc-type

Re:Chrome’s requestAutocomplete() by r00fus on Thursday May 16, 2013 @01:50PM (#5719906)
1Password allows one to autofill credit card, address and other fields as well, you know. I use that almost as frequently as the passwords.
Re:Chrome’s requestAutocomplete() by sinofer on Thursday May 16, 2013 @03:26PM (#5720583)
I use lastpass for the purpose. But I can imagine baking it into the browser will lead to higher conversion rates especially on mobile.
Re:Chrome’s requestAutocomplete() by tomjen3 on Thursday May 16, 2013 @02:40PM (#5720287)
I wouldn't be surprised if 1PW works with autocomplete data pretty soon.