4 ms·
> autocomplete="nope" wat. Developer gag left unchecked?
by Jenk 6y ago
> autocomplete="nope"
wat. Developer gag left unchecked?
- themacguffinman 6y agoIIUC "nope" used to be effective at disabling autocomplete because it's an invalid autocomplete value which Chrome treats differently from "off" (which it ignores) or "on" (which enables autocomplete). Chrome 81 should already have fixed this quirk.
- deleted 6y ago[deleted]