[whatwg] A mechanism to improve form autofill

James Hawkins jhawkins at google.com
Fri Aug 3 10:36:09 PDT 2012

On Fri, Aug 3, 2012 at 5:31 AM, Aryeh Gregor <ayg at aryeh.name> wrote:

> On Thu, Aug 2, 2012 at 9:42 PM, Ian Hickson <ian at hixie.ch> wrote:
> > On Thu, 26 Jul 2012, Smylers wrote:
> >> Ian Hickson writes:
> >> > > Also, I do not understand why we have credit cards types. Is anyone
> >> > > willing to have his credit cards information saved locally?
> >> >
> >> > Sure, why not?
> >>
> >> I am too, but I can understand why people who share their computer (and
> >> user accounts) with others wouldn't want their card numbers saving.
> >
> > That's a UA configuration issue, presumably. (Similar to saving
> > passwords.)
> In fact, Chrome already autodetects credit card numbers for autofill
> (presumably based on a heuristic) and has a special dialog for whether
> to remember them, similar to the password-remembering dialog.  At
> <chrome://chrome/settings/autofill>, there are fields for both
> addresses and credit card numbers.  This is documented here:
> <
> https://support.google.com/chrome/bin/answer.py?hl=en&answer=142893&p=settings_autofill
> >
>  IIRC, one option when it asks you to remember credit cards is "don't
> ever remember credit card numbers" -- although I'm not sure, since I
> think I picked it and thus haven't seen the dialog in a long time.  :)

In practice the credit card portion of Chrome Autofill is not very useful
since most (hand-wavy) sites that contain credit card fields in forms use
autocomplete=off, which Chrome respects.  There is a third-party Chrome
extension which removes autocomplete=off to solve this issue.


More information about the whatwg mailing list