Feature request for pages with sign up & sign in forms
Many landing pages have both sign up and sign in forms on the same page. Some will us JS to show the sign in form when you click the sign in link.
Why not have the browser extension look at the submit button for each form on the page decide which to fill in.
If the submit button for a form includes words like 'up', 'started', 'free', 'trial', etc. then it's probably not a sign in form.
Comments
-
Hi @weavermedia,
Thanks for the feature request! Are you having trouble getting 1Password to fill the correct sign in form on a page like that? If so, that can often be solved by saving a new Login item by following the steps in this knowledgebase article. If you try that, does the new Login item fill the correct sign in form?
If that doesn't help, would you be able to let us know the URL for the site where you're having this problem? If we can test that ourselves, we should be able to figure out what's happening. Thanks! :)
0 -
Thanks for your reply @Drew_AG - here are a couple of sites where I've had problems:
https://www.samplemagic.com/ - 3 forms next to each other, Register, Mailing List, Sign In. 1P fills Register instead of Sign In
https://distrokid.com/ - Sign In form is revealed on click but 1P fills the Sign Up form already on the page.
I appreciate you pointing me to the KB article but I don't feel like these kinds of things should need manual intervention from the user. The forms are clearly labelled on the pages, the browser extension should be able to see that.
0 -
Hi @weavermedia,
Thanks so much for the URLs! I tested each site by entering info in the Sign In form and manually saving a Login item using these steps. In both cases, 1Password was able to fill the Sign In form correctly. If you follow those same steps, it should work correctly for you too.
I don't feel like these kinds of things should need manual intervention from the user.
The reason that's necessary takes a little explanation for how 1Password saves and fills login details. When 1Password saves a new Login item, it saves the contents of the fields on that website (i.e. what you've entered) as well as other attributes about the form's fields, such as their internal field names (which are often different from the visible field names you normally see on the site). 1Password saves those form field attributes (and the contents of those fields) as web form details in the Login item. When 1Password fills your login credentials into that same form on the same site, it uses those saved form details to determine which fields to put your username/password into.
The internal form details of registration forms and login forms can be very different from each other, even if the visible field labels appear to be the same. On many sites, the registration and login forms are on completely separate pages from each other, so if the Login item was saved from the registration form, 1Password can't rely on the web form details to fill the login form, and therefore uses different logic to do so. This often works when the registration and login forms are on two different pages, because it's usually easy to determine the best matches for the username and password fields.
However, on the sites you mentioned, the registration and login forms are on the same page. So if you enter your data in the registration fields and save a Login item, 1Password remembers that, and will fill your username & password in those same registration fields. Alternately, if you enter your data in the login fields and save a Login item, 1Password will remember that and fill your username/password in those same login fields (which is why these steps to save a new Login item will solve the problem).
I suppose this is a long way of saying that 1Password tries to fill your username and password into the same fields of the same web form as you did when that Login item was saved. It offers to save a new Login item when you fill out a registration form because it doesn't want you to lose that information, but it is sometimes necessary to save a new Login with the correct fields filled out so 1Password can reliably fill it the same way in the future.
I hope this helps, but as you can tell, it can be rather complex, so please let us know if you have more questions about that! :)
0