autocomplete: autocomplete="off" does not work in chrome
See https://bugs.chromium.org/p/chromium/issues/detail?id=370363#c7
Expected behaviour: chrome native autocomplete is not drawn on top of autocomplete.js autocomplete.
Workaround (either):
- use autocomplete=“new-password”
- insert input
<input style="opacity: 0; position: absolute" />right before your autocompleted input
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 18 (12 by maintainers)
Just a heads up, it seems the latest version of Chrome is ignoring
autocompleteattribute regardless of what your usingnopeor `off.nopecomes from https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletionI observed the issue on my machine and changing
autocompleteseemed to fix it.@Haroenv I’m looking for the Google Bug ticket link but it was a 1.5 months ago, Google may have re-enabled watching it again. Not a ton that can be done anyway until Chrome starts respecting the attribute 😄
Here you are @Haroenv ^
@Braunson does it work for other browsers like safari/firefox?
@Haroenv I’m still observing weird autocomplete behaviour with proposed double-input fix on local environment, however it works on prod. 🤷♂️Will investigate on my side and post the results here.
ugh, this is extremely annoying. Sorry that we can’t fix this any more than already done. Thanks for the heads-up @Braunson.
Do you know of a write-up somewhere on the situation?
Can’t promise, but will try to find time to do a pr on weekends.
Thanks for your detailed bug report by the way, we will try to see if we can find a solution. It might be quite simple to implement here since we already have two inputs. It would be really nice if you already have to solution to take a look if you can do a PR 😄