-
HenrikJoreteg this bit me as well. Chrome is ignoring “off” on purpose, going against the spec. There is an open issue where they evaluate that behavior though. Wordaround for now is to use an unknown invalid attrivute, I’ve choosen autocomplete="off-even-in-chrome"
-
HenrikJoreteg update/correcting: current Chrome Canary (v69) is now respecting
autocomplete=off
again (and only that value turns it off, complete reversal of previous behaviour!)