3 ms·
> As an example, if you have an address input field in your CRM tool that you don't want Chrome to Autofill, you can give it semantic meaning that makes sense r
by JungleGymSam 10y ago
> As an example, if you have an address input field in your CRM tool that you don't want Chrome to Autofill, you can give it semantic meaning that makes sense relative to what you're asking for: e.g. autocomplete="new-user-street-address". If Chrome encounters that, it won't try and autofill the field.
Seems reasonable to me.
- kuschku 10y agoExcept, Google themselves now do "google-chrome-autocomplete-off" and "both" and similar values instead. We just replicated the PHP or IE situation with mysqli_real_surely_this_time_it_works_escape_string or autocomplete="sudo-off".
- dragonwriter 10y ago> Except, Google themselves now do "google-chrome-autocomplete-off" and "both" and similar values instead. That's clearly a suboptimal practice by Google's web team. Which doesn't make Google's Chrome team wrong, but maybe the latter should have a word with the former.
- kuschku 10y agoWell, there’s no alternative. You don’t want the Google search box, or the hidden textfield in Google Docs, or so, to autocomplete.
- dragonwriter 10y ago> Well, there’s no alternative. Sure, there is. You could do a meaningful semantic autocomplete tag that isn't one of the recognized ones, rather than a variant of "no, really, don't autocomplete this". (Actually, "body" is probably not a bad practice, but the other one was.)