4 ms·
I was asked by my users of an internal tool to disable autocomplete. I added autocomplete="off" and autocorrect="off" (spell checking makes no sense for this f
by banana_giraffe 6y ago
I was asked by my users of an internal tool to disable autocomplete. I added autocomplete="off" and autocorrect="off" (spell checking makes no sense for this field), and it was disabled, including for chrome users.
Am I missing something? Is there some sort of heuristic to when it actually disables that I just got on the good side of by pure luck?
- eternalny1 6y ago> Am I missing something? Is there some sort of heuristic to when it actually disables that I just got on the good side of by pure luck? Yep, you are. Chrome will fill in fields by not just looking at the autocomplete attribute, but also by trying to magically infer it based off the name attribute (and other heuristics). For example, if you have a text entry box for a filename, and happen to set "name='name'" on it, even with autocomplete off you will get a pick list of people's names. https://developers.google.com/web/fundamentals/design-and-ux/input/forms#use_metadata_to_enable_auto-complete https://developers.google.com/web/fundamentals/design-and-ux...
- banana_giraffe 6y agoInteresting, the label for this field is Name, but lucky for me I guess that I gave it a silly name based of the database field it maps to.