Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Google Chrome forces autofill on fields set autocomplete="off"

See original GitHub issue

We are struggling to disable chrome’s autocomplete when using this. We can set autocomplete: "new-password" on the input, but not on the new input in the autocomplete__wrapper. You can see chromes autofill interfering and the relevant autocomplete label in this screencast.

From researching it this morning it seems to be that Chrome is ignoring autocomplete “off” and instead you need to use “new-password”.

Chrome intentionally ignores autocomplete=“off” and autocomplete=“false”. However, they put new-password in as a special clause to stop new password forms from being auto-filled.

from https://stackoverflow.com/questions/10938891/disable-form-autofill-in-chrome-without-disabling-autocomplete

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:12 (6 by maintainers)

Top GitHub Comments

8reactions

dashousecommented, Feb 6, 2019

Stolen from @igloosi’s Twitter

chrome-autocomplete

3reactions

NogginBoxcommented, Jul 12, 2019

@nickcolley I’ve been struggling with this bug in Chrome for a long time. The chrome team do not seem to be paying attension to the bug report and seem to actively find new ways to force autocomplete, when you think you’ve found a work around.