5 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 koolba 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.
Reminds me of the good old days of making things work with IE6.
> Again, thanks to everyone for your comments. We look forward to continuing the conversation.
Sure you do. Then why is commenting closed?[1]
[1]: See the "Restricted- Only users with EditIssue permission may comment." box on the left pane.
- md224 10y ago> Sure you do. Then why is commenting closed? From the post: > All this said, we're still learning. So we would like to better understand your use cases for setting autocomplete=off. To have that conversation in a more focused manner, I've created a new bug: crbug.com/587466. We're going to try and keep that conversation focused and productive, so we want to avoid "+1s" and the like. I'll be closing this bug in the meantime. Commenting is open at https://crbug.com/587466 https://crbug.com/587466.
- koolba 10y agoAh! Well that's what I get for skimming through the post. I stand by the IE6 comment though.
- deleted 10y ago[deleted]
- edibleEnergy 10y ago'The semantic meaning' hack is bad for readability. You don't actually mean 'new-user-street-address' you mean 'do not autofill this input chrome.' The next developer in will assume the semantic meaning accomplishes something, and decorating your markup with things that may or may not do nothing seems is bad practice.