EDIT: Solved. I found how to create a custom field using âInspectâ for the problem field. The field was a ridiculously long ID. (right click the field, Inspect, look for the field ID and copy it to a custom field in Bitwarden.)
I'm having a similar problem. How can I find the name of an input field so I can create a custom field that matches. My password is being filled in on both the username AND password field.
Hmm⌠this doesnât seem to work on Android, either on my phone or on my tablet. On those it still fills in the password in both the userid and password fields.
It works the same on Android. But perhaps you get a different version of the login page and therefore the field might have a different ID.
To see the source code within Google Chrome on Android add view-source: infront of the URL.
This âview-sourceâ method gave me the source for the entire page. I couldnât find the input Id, so downloaded an app called Inspect and Edit HTML from the play store. It allowed me to âInspectâ the actual input field for the password. The Id â_ParticipantLogon20_WAR_ahcommonauthportlet_userIdâ and source code are identical to Chrome and Firefox on Windows, Linux or Chromebook. (these work fine) This is for the Lumen benefits website. Bitwarden isnât filling in the UserID on either my tablet or my cellphone. It puts the password in both the userid and password fields.
I left the username field in Bitwardenâs Lumen entry empty. I made a custom field for the userid.
Possible bug in the string length of the fields in the android version?
The website is: https://leplb0330.upoint.alight.com/web/centurylink/login/
The two fields are:
â_ParticipantLogon20_WAR_ahcommonauthportlet_userIdâ
and
â_ParticipantLogon20_WAR_ahcommonauthportlet_passwordâ
If you put âm.â in front of the web version of the website URL, you may get the mobile version, then inspect that for the possible new mobile field name.
If that website you mentioned is using some kind of plugin that happens to connect to Paypal, it may have nothing to do with Paypal. They might be doing a passthrough.
For your particular situation, I would recommend waiting for someone from Bitwarden to comment (or someone who has worked with android AutofillService).
Based on information I have seen, I donât think it is possible to autofill Custom Fields on Android either due to API limitation (or current Bitwarden implementation?).
However, I donât code mobile apps and I havenât worked with C#/Xamarin, so I donât have full details.
I will provide basic notes below based on quick skim though your example site, the android docs, and Bitwarden code.
Your particular website
I think the issue with the site you are using is that the Username field is using type="password" along with the odd id/name.
This is confusing Bitwarden into thinking the field is for your password.
EDIT: This is something Bitwarden Mobile app checks to detect passwords.
Android Documentation
Based on skim through Android documentation, Android mainly uses:
a fixed set of supported âautofill hintsâ (usually basic info like username/password/phone/postal_address), or
the website needs to provide a special âautocompleteâ attribute.
Not too sure if possible to obtain HTML id / name attributes and run Custom Field logic. Would need Android developer to comment on behavior.
Bitwarden Mobile Code
I didnât really look too much into this, but I could only find autofill logic to handle username/password.
Some day, hopefully, myopic website developers will realize that tens of millions of people around our amazing planet use password managers, and they will choose to design websites that work easily with them.
Honestly, itâs not hard. Itâs just a bad combination of myopia and laziness.
Last I checked, popular sites like Yahoo and Evernote still donât play well with password managers; they require users of password managers to enter their credentials twice because they donât have the input fields for the username and password loaded in the DOM at the same time.
Fixing this is a simple task, but not making these mistakes in the first place would be even better.
My solution is, whenever possible, to not use sites or services that do not play well with password managers. For this reason, I no longer have a Yahoo, Evernote, or PayPal account. No Google account either, but thatâs due to: Add unshare option - #137 by bit
Too many great options to deal with ineptitude or ignorance these days. Thatâs why I no longer have a LastPass account either!