The Chromium team, in its infinite wisdom, has decided that web applications that specifically say to disable autocomplete are just wrong, and it ignores those requests. They offer a workaround (setting "autocomplete" to a semantically-meaningful value that will be ignored), but that doesn't really work; it turns off one kind of autocomplete in favor of another.
Possible resolutions:
Use Firefox instead, since it seems to respect the application's wishes.
Manually configure Chrome to turn off autocomplete.
Have client installation that turns off autocomplete.
Use kiosk mode, which seems to disable autocomplete.
Accept autocomplete. (Doesn't seem like a good idea.)
Kiosk mode has the advantage of also taking the page full screen, ref #74.
jordanbrown0
commented
2 years ago
The Chromium team, in its infinite wisdom, has decided that web applications that specifically say to disable autocomplete are just wrong, and it ignores those requests. They offer a workaround (setting "autocomplete" to a semantically-meaningful value that will be ignored), but that doesn't really work; it turns off one kind of autocomplete in favor of another.
Possible resolutions:
Kiosk mode has the advantage of also taking the page full screen, ref #74.