2

Autocomplete true|false, on|off no longer appears to be valid Hiding in plain sight a text input, and password input before the legitimate one that needs to be accessible to the UI doesn't work. And dynamically clearing the input the username is put in isn't an option as we pre-populate that input on a number of legitimate reasons.

Also worth noting is it also appears that the input in question is populated by chrome despite being populated by what it should have been populated by.

Is there a clean solution for this behavior, as its rather problematic overall from a UX perspective.

chris
  • 31,824
  • 49
  • 132
  • 238
  • If the field has to be populated by your code, can't you just set it to `readonly`? – Eric May 16 '16 at 17:06
  • Have you tried http://stackoverflow.com/questions/15738259/disabling-chrome-autofill?rq=1 – Erick May 16 '16 at 17:09
  • Read Only wouldn't work as it is acceptable for the user to modify the input in question. We store the state if they ever changed it previously, and populate it for convenience. But all in all its changable – chris May 16 '16 at 17:15
  • Trying the fake user/password inputs is something I currently try, and it worked for a while. It like autocomplete seems to not work anymore. – chris May 16 '16 at 17:15

0 Answers0