AutoFill is inconsistent

shaowei
shaowei
Community Member
in 1Password in the Browser

Here's an example to reproduce the issues that I came across.

Issue 1

  1. Go to https://www.cordlife.com/sg/client-payment (it's a payment site for Cordlife, it's a legit website and no payment will be made as long as no submission is done).
  2. Fill up the form randomly for testing purposes. However, make sure to set Service Type (form field form[Service][]) to "Cord Lining Storage", and set Bank's Name (form field form[Bank][]) to "American Express" (this is for triggering issue 2).
  3. Use the "Save Login" method of 1Password Extension (I am using it from Vivaldi 3.7.2218.55 (Stable channel) (x86_64)). Let's save it to "Cordlife (Auto)".
  4. Refresh the Cordlife page, and attempt to AutoFill using "Cordlife (Auto)".

Expected

The fields are all filled in.

Actual

There are missing fields.

Issue 2

  1. Go to 1Password on macOS to create an entry from scratch, say "Cordlife (Manual)".
  2. Copy content of "Cordlife (Auto)" to it, entry-by-entry.
  3. Using the "View Saved Form Details" option to gain access to the saved form entries in both "Cordlife (Auto)" and "Cordlife (Manual)". Copy across everything verbatim.
  4. Refresh the Cordlife page, and attempt to AutoFill using "Cordlife (Manual)".

Expected

The exact same fields as previous are filled in (despite being incomplete)

Actual

Service Type & Bank's Name are both not selected.

For issue 1, it seems that it's that the form data are being stored as login entries instead of form details. I am not sure why that workflow, but I guess it is a feature decision of 1Password, e.g. I guess it's to expose those data yet hide the form details. If it's me I would expose all form data and title it to caution the clueless users from altering them. I doubt there's a perfect solution, but the current one sacrifices correctness too much. In comparison LastPass is much more inflexible compared to 1Password -- it can only provide url/username/password and everything else go to form field. However, it has nailed AutoFill already since the time I was using it 4 years ago.

However, I would consider issue 2 a bug. I would think that all behavior should be dependent on the state of the entry. So if I am to create 2 login entries in 1Password with the exact same content, then their behavior on the corresponding website should be exactly the same. I wonder what additional information could be hidden by "Cordlife (Auto)" that resulted in this difference...

This thing has frustrated me the whole afternoon, and hopefully it's just that I screwed up somewhere and there's a way to properly make sure that we can fill up everything in that form. I would be glad if your team try out filling https://www.cordlife.com/sg/client-payment yourself first and suggest me a method that can work.

Sorry for the inconvenience, and thanks much for the effort put into answering my questions. Cheers!

1Password Version: 7.8.1 (70801003)
Extension Version: 1.24.2
OS Version: macOS 11.2.3 (20D91)
Sync Type: Not Provided

Comments

  • ag_yaron
    ag_yaron
    1Password Alumni

    Hey @shaowei ,
    Thanks for taking the time to write about this.

    The issue here is that this page is not a login page (it has no username and password fields), and you are trying to save it as a login item in order to save time and be able to autofill that page, which is perfectly understandable.
    Since this is not a login form, 1Password won't capture some (or all) of the fields on the page.

    However, we've added improved support for such saving scenarios in our latest beta, and I can confirm I was able to save all fields properly with that beta. I'd like you to try it:

    1. Disable/remove 1Password from your browser.
    2. Install the latest beta version: https://support.1password.com/betas/#install-a-beta-release-of-1password-in-your-browser (Select the Chrome one if you are using Vivaldi).
    3. Test things by saving a brand new login item on this page after you manually fill in all of your details.
    4. After you autofill, one of the dropdowns selection menus will prevent the invoice number and contract number fields from being filled in, so simply click inside one of them and autofill again.

    As for issue #2, that is not exactly an issue but more of a transition period we're currently in. We are moving away from the saved form details section and instead are utilizing the custom fields section for autofilling fields that are not usernames/passwords. Currently some things are still saved in the saved form details but the important part is the custom fields section (under the website's URL) in the item.

  • shaowei
    shaowei
    Community Member

    Oh my! Thanks so much for the detailed explanation @ag_yaron! My issues are understood and addressed fully. You even went to try out the filling yourself! By now the feature you mentioned has been pushed into the main app. I've just tried it and it works great. Apologies that I didn't catch this reply earlier and help to review the beta before the launch >_<

    I understand from your reply that issue #2 is due to a transition to a different implementation. For now, as long as the "Save Login" method works, I'm good! :+1:

    All the best at 1Password. I look forward to future improvements that make it even better.

  • ag_yaron
    ag_yaron
    1Password Alumni

    I'm glad to hear everything is working well for you on the stable version now @shaowei !

    Thank you for the kind words as well. Enjoy your 1Password :chuffed:

This discussion has been closed.