Safari extension fills old details instead of current ones

Hi @norysang,

As per your request, I am posting the explanation of the issue and the workarounds for more exposure:

Lots of websites will use email address as username, which is normal. However, when a website is using email as the username value and the login item in 1Password has another (old) email field saved, 1Password might get confused when autofilling.

For example, this website uses email info as username in the login form, however, the website's username input field only contains HTML attributes that are related to "email", there is nothing mentioned about "username", see screenshot below:

When we have a login item for a website like the above and there is an "email" field saved within it, like below:

In the consideration process for autofilling, 1Password's brain is doing the math for the username/email field. The actual "email" field takes more weight in the calculation, and then, 1Password decides to use the old email info in the "email" field, rather than the current/actual email info in the default username saved in the login item to autofill on the website. That's how the issue/confusion is formulated.

We have two workarounds for this situation:

1. We can change the title of the old email field, for example from "email" to "Oldemail" (no space in between). Then, there is no match between the changed title of the email field and the HTML attributes of the email field on the website. So, the weight of considering for autofilling will be deducted and the actual email saved in the username field will be prioritized.

2. Instead of creating an "Email" custom field in 1Password, we can create a "Text" field and name it email:

• 

• This way, the "Text" field will take less portion compared to the "Email" field in the autofilling consideration process, so 1Password will still use the email saved in the default username field.