FQDN match only prioritized for first website

edited April 2019 in 1Password X

Let's say I have login A with the website set to https://example.com and login B with the websites set to and https://foo.example.com. In this case, filling on https://foo.example.com will simply sort A before B alphabetically. However, if I swap the two URLs for login B and put https://foo.example.com first, the FQDN match is correctly sorted first.

This is not a huge concern in my case as swapping the URLs resolves the issue but it may become a problem in more complex cases.

1Password Version: Not Provided
Extension Version: 1.14.3 (Chrome 73)
OS Version: Windows 10
Sync Type: my.1password.com


  • Greetings @nyuszika7h,

    So I can reproduce the bad behaviour you're seeing and the good news is I'm not seeing it in a nightly build. It looks like we've corrected the issue and so it will hopefully just be a case of waiting for the improvements in the private nightly build to trickle down into first the beta and then stable. Thank you for reporting it though as it could easily have been something we weren't aware of yet.

    ref: x/b5x#837

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file