For a while now, whenever I try to log in to Binance on the web, Bitwarden does something strange. As soon as my email is suggested or I use the FILL button, the Binance “username” field switches to a phone number field and then gets autofilled with my TOTP code (I use Bitwarden’s TOTP option).
On the Binance login page, if you type three digits into the username field, it automatically turns into a phone number field. But my email address has no numbers in it, so that shouldn’t be triggered. This also doesn’t happen on iOS.
In a short test, I wasn’t able to autofill at all on https://accounts.binance.com/en/login. Here the link to the form for reporting autofill issues: Report auto-fill failure
PS: And/or… change to passkey login on their site.
@leomozoloa Welcome to the Bitwarden Community Forum!
Try adding a custom field of the type “Linked” (linked to the Username), and making the field label Username field for email or phone number, as shown below:
It’s not a work-around, as it is the officially documented technique to use when there are any “issues autofilling usernames and passwords for a particular site”.
Because there are no relevant standards in website development, there will always be some fraction of websites that have username or password fields that cannot be automatically recognized by Bitwarden — or any other password manager (although the sites that fail will differ for each product). Fields can only be recognized as a username or password field by examination of the text labels (visible and invisible) that the web developer has used to identify or annotate the field (and to a certain extent, by examining the relative proximity of fields, since username & password field are often are paired). There is an uncountable number of possibilities for such labels (including labels like afi-692e380f5a71 that have no meaningful interpretation), so no password manager will ever be able to create a comprehensive list of label examples to use for identifying username and password fields (not to mention the fact that more extensive lists will increase the probability of false positives, in which the password manager autofills a field that should not a username or password field). Even incorporating an LLM will not solve this problem — accuracy may improve (at a significant cost of performance), but never to 100%.
You can use the Autofill Failure Report form to notify Bitwarden devs about the issues with the Binance website (in the hopes that they create a fix for this one website), but in the meantime, the answer given aboveis the solution (and withholding a solution mark will in no way have any effect on the chances of Bitwarden possibly developing a code change to address the Binance issue).
I understand but I thought bitwarden had a list of the top 100 or so websites that have non conventional fields and though binance would be in it. I filled the form
solution mark will in no way have any effect on the chances of Bitwarden possibly developing a code change to address the Binance issue).