awesomplete: autocomplete="off" doesn't work in Chrome

using autocomplete="off" does not stop Chrome’s autofill from working.

The current workaround is to pass a random value to it

I use autocomplete="nope" and it works great. You can put in any string value that is not “off” or “on” in there.

I suggest autocomplete="awesomplete"

https://www.20spokes.com/blog/what-to-do-when-chrome-ignores-autocomplete-off-on-your-form

https://stackoverflow.com/a/38961567/395414

link to the spec

About this issue

Original URL
State: open
Created 6 years ago
Comments: 15 (8 by maintainers)

Commits related to this issue

Add "autocomplete" as initialization option (#17159) Hi 👋 ! I have the same issue as #17155, but I suggest a slightly different modification. I don't know if this is a priority but I feared that ... — committed to LeaVerou/awesomplete by antoinelyset 6 years ago

Most upvoted comments

I guess I should release a new version with the revert. Would that work for y’all? If so, I can do it later today.

LeaVerou on Oct 19, 2018

Happy new year!!

Done, thanks for the ping! Now if only I could find some time to review all the outstanding PRs… 😕

LeaVerou on Jan 7, 2019

Ugh, so I guess if it didn’t fix it in Chrome and it broke it in Firefox, I’m gonna revert it until we figure out the best course of action.

LeaVerou on Sep 21, 2018

@LeaVerou Hate to bug but can we get an update on this? (Happy New Year 🎉 )

adamgruber on Jan 2, 2019

Is there an anticipated timeframe for releasing the reverted change made in https://github.com/LeaVerou/awesomplete/pull/17162?

adamgruber on Oct 8, 2018

@antoinelyset your PR seems to have broken the autocomplete behavior in Firefox 63. I’m now seeing the native autcomplete menu on top of the Awesomplete menu:

screen recording 2018-09-21 at 01 38 pm

blvrd on Sep 21, 2018