I cannot reproduce this issue in a Chrome browser extension on Windows 10.
You can try to make this work using custom fields. First clear the username field so that it doesn’t get autofilled anywhere. Then create a custom text field named InputLabelled_2, with a value that should be your login email. Next create a custom “linked” field named InputLabelled_3, with the value linked to your Password. Let us know what happens with this configuration.
I know, but I am only able to test on Windows. So the problem appears specific to the mobile version of Chrome. Perhaps the website serves a different version of the login page when it detects a mobile device. In any case, it is possible that the custom fields method that I have suggested may work for you, so I would suggest trying it and reporting back.
Hi! I tried the custom fields and it’s still putting in the email address as the password. Also even though I followed your instructions exactly, it looks like something is wrong with the password as opposed to the username field. I’ve attached a screenshot
Hi grb I realised I had not followed your instructions to the letter so I tried again, and now it fills the password in twice on the website. Screenshots attached.
Not sure what is going on, but I think there is still one detail that you didn’t follow. For the custom field named InputLabelled_2, do not make it a linked field. Make it a regular Text field, and set the value to be your email address (the email that you use to log in to this site). Let me know what happens when you make this change.
Okay I followed the directions. You were right I didn’t see that you wanted the username login to be text. It still doesn’t work, it puts the password in twice, for username and password.
Clear your password from the Password field, and delete the linked custom field InputLabelled_3. Then test if autofilling at least fills your email into the correct location. If not, we’ll need to investigate further.
Next, add a new custom field that is of the type “Hidden” (not Linked or Text), set the field name to InputLabelled_3, and set the field value to your password.
This was a stubborn one - I could get the desktop page to fill no problem, but using Chrome on Android 12 it was doing nothing until I entered in the following - maybe it will work for you too, @Atilertse_W:
Thanks for the advice but using your method it ended up with the same problem - filling in both fields with the email address here’s a picture, did I do something wrong?
In your two custom fields, it looks like you may have created custom fields of the Text type and just typed in the words “Password” and “Username” for the text values. They are supposed to be custom fields of the Linked type, and be linked to the Password and Username fields, respectively.
hmm so one thing I tend to do which works on multiple platforms not sure if anyone mentions is physically label the text field to what I want it to fill into and so far it always work that way. If a text field on a website says “email” or “email address” I will have a custom
field created showing that many times of course the username for some websites may not be your email address.
i created a test version below to show you what i mean.
also tested out on the website and got no issue. the standard username field worked and the email one did as well inputting items in the correct fields.
here’s a picture, did I do something wrong?
