- From: Ben Maurer <ben.maurer@gmail.com>
- Date: Thu, 13 Nov 2014 21:57:28 -0500
- To: Evan Stade <estade@chromium.org>
- Cc: WHAT Working Group Mailing List <whatwg@whatwg.org>
If the site sets autocomplete=off could you disable the saving of new suggestions? One of the main use cases for turning off autocomplete is to disable the saving of sensitive or irrelevant information. If the user is filling in an address or cc num it's likely they have the opportunity to save that on other sites. Sent from my iPhone > On Nov 13, 2014, at 2:20 PM, Evan Stade <estade@chromium.org> wrote: > > Hi, > > Chrome already ignores the prevalent autocomplete="off" for password > fields. We plan to ignore this tag for Autofill (addresses, credit cards) > fields as well. autocomplete="off" will still be respected for autocomplete > data (e.g. past searches on crbug.com). > > We think this will break a very small number of sites that use > autocomplete="off" for legitimate reasons, e.g. they use the Google Maps > Places Autocomplete API, and don't want Chrome trying to autofill in > addition. But it will improve behavior for a much larger set of sites which > use autocomplete="off" for confused reasons as a part of, e.g., their > checkout flow. We have found the prevalence of autocomplete="off" in top > sites' checkout forms to be quite high. > > Currently this new behavior is available behind a flag. We will soon be > inverting the flag, so you have to opt into respecting autocomplete="off". > > I am curious what other browsers do around autocomplete="off", and if they > respect it for address/user profile/credit card type data. Since there's no > way to feature detect the browser's behavior, it would be convenient if all > browsers agreed on the meaning/value of the attribute. > > -- Evan Stade
Received on Friday, 14 November 2014 02:57:55 UTC