Search fields are autofilled with user name when Shield enabled
-
Hello, Shield team,
Here’s a problem that’s been around for a while:
Whenever Shield is enabled, Chrome auto-fills login data into fields where it doesn’t belong, e.g. the search filter field on the media library. Now, I can’t see any of my media.
When I empty the field, the user name comes back after a few mouse clicks. This happens only when Shield is enabled.
Up until a while ago, Chrome had an option to stop this autofill feature and only show user data as a dropdown when one clicks on the field. However, that option was recently nixed.
I’d love to keep using Shield and hope you can find out what’s causing this.
Thanks!
Matt.The page I need help with: [log in to see the link]
-
Hey Paul! I find it absolutely mystifying as well. The bad news is that Google removed that option to disable the autofill (it was one of the “experiments” you can access through chrome://flags).
This started happening in Chrome in mid-2019, when numerous users reported the behaviour.
https://support.google.com/chrome/thread/9498749/chrome-auto-filling-field-incorrectly?hl=en
Here, you can see that the issue also happens e.g. in Synology’s DSM:
https://community.synology.com/enu/forum/1/post/125139?page=2&sort=oldest
Chrome used to have the flag, “Fill passwords on account selection”, which helped work around the issue. However, they removed it in late April in Chrome version 101:
https://lapcatsoftware.com/articles/Chrome101Fill.html
But hey, I just discovered that there’s a bug report about it and it seems the Chrome devs are putting the flag back in the upcoming version 102:
https://bugs.chromium.org/p/chromium/issues/detail?id=1320044
Still, if there’s any way you can work out why Chrome thinks this search filter field is a user login field, I think it would help other users facing the same issue and not being aware of the Chrome flag.
- The topic ‘Search fields are autofilled with user name when Shield enabled’ is closed to new replies.
