Re:Valid use cases for autocomplete=off
by Sohcahtoa82 on Friday September 28, 2018 @08:31PM
(#18098045)
> Have a look at the address field on this image - you can see that autofill completely obscures Googles own autocomplete (which is a paid service) https://00e9e64bacbf59c74081b665c25aa171225f21f85c7201a66c-a.... That's not good for users.
You may want to reupload that image to an image hosting service. When I click that link, I get a page that says:
{"error":{"errors":[{"domain":"global","reason":"lockedDomainExpired","message":"Locked Domain Expired"}],"code":401,"message":"Locked Domain Expired"}}
It's no longer up to you as a developer whether or not you think a field should autocomplete - Google has decided that for you.
Have a look at the address field on this image - you can see that autofill completely obscures Googles own autocomplete (which is a paid service) https://00e9e64bacbf59c74081b665c25aa171225f21f85c7201a66c-a... That's not good for users.
You simply cannot turn off either autofill or autocomplete.
Further info: https://stackoverflow.com/questions/29931712/chrome-autofill...
Please, if you care about autocomplete=off then register a comment on the Chrome bug https://bugs.chromium.org/p/chromium/issues/detail?id=587466
The strange thing is that this even breaks Google's own paid Google Maps autocomplete service - search the text in the linked Chrome bug page for "maps" to see what people have to say about that.