Browser Form Autofill
Discussions center on how a form technique or UI change interferes with browser autofill features, including Chrome's automatic filling, password managers like LastPass, and workarounds like autocomplete='off'. Concerns include usability loss, phishing risks, and browser behaviors ignoring disable flags.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Does anyone know how this interacts with form auto-filling?
But then the browser won't autofill it, so what's the problem?
It looks like the UI would clash with the browser's autofill recommendations.
Would this also stop users with automatic form filling enabled?
i dunno why you're getting downvoted. you're right about this. but this doesn't apply to autofill behavior of non-password fields.
autocomplete in chrome fills in the forms without user interaction, the user doesn't get the choice, they can only wipe the fields afterwards if they happen to notice.
autofiller wouldn't trigger on a phishing site
Forms are annoying and should to the greatest extend be automatized. Chrome autofill and saving user's input is helpfull.
I wonder his this fares with auto-filled forms by the browser and things like lastpass / onepassword
MDN literally mentions jquery.disableAutoFill which basically does that for you under the cover (scrambling the name on display, and unscrambling on submission).