3 ms·
Ah, thanks, I didn't do it on purpose, I was just confused. Because: > our suggestion at this point is to utilize the autocomplete attribute to give valid, se
by jrochkind1 10y ago
Ah, thanks, I didn't do it on purpose, I was just confused. Because:
> our suggestion at this point is to utilize the autocomplete attribute to give valid, semantic meaning to your fields. If we encounter an autocomplete attribute that we don't recognize, we won't try and fill it.
How is a value not allowed by the spec "valid" as they say? They're encouraging you to violate the spec to trigger chrome-specific behavior (can't really say what other browsers will do when spec is violated, can you?), really? Or does the spec say you're allowed to make up new values too? i don't _think_ so, but maybe I missed that part (not being sarcastic).