Autofill... domain matching choices?!? O. M. G.

Good to hear! Let me know if I can help further.

Ah, okay. I already got this Autofill Behavior menu back with the latest beta build. It was gone in latest production release, that I got some days ago. Everything's fine now. Thanks!! 👍❤️

DenalB I was referring to the issue you were experiencing where the Autofill Behavior menu is not showing up. I am currently unable to reproduce this issue because I'm on a production version that's newer than the latest beta, but switching to the nightly on my end does cause the menu to show. Wondering if that would work for you too.

Hey @ag_Gabriele !

Actually, I'm on the latest beta - 1Password for Windows 8.10.0 (81000009). What should I test in nightly build?

DenalB could you try switching to the Nightly channel, updating, and letting me know?

You won't be able to get back to Beta directly after updating to Nightly, however if you set the channel back to "Beta" directly after updating you'll automatically get updated to the next Beta when it's available.

Hi! (just a quick suggestion) As much as I'd like the "scoring system" to always default to the correct suggested logon automagically, I guess it will always be some exceptions and/or overrides needed - at least in my (possible) "corner cases". No reason to "reinvent the wheel" here; Bitwarden has some simple, but (really) powerful options, where the end user can choose between e.g. "Starts with" (URL) and "Regular expression" (regex), which I think will cover many, if not most cases (at least for me).

If possible, also prefer having an option(s) to select what fits best in each of my cases (which will be different from other users, hence having an option is preferred), like choosing "Starts with" or "regex", based on my needs, in each case, not having the back-end trying to automagically "be smarter", by selecting something else.

(from Bitwarden, default options for each URI per entry):
* Default match detection
* Base domain
* Host
* Starts with
* Regular expression
* Exact
* Never

Screenshot

Regarding the ordering, LastPass (in lack of other features) had a solution, where basically it followed the name of the item, ascending. "Account A" (match) will be displayed before "Account B" (match), etc. A bit simple, but it might work (in some cases). Also really easy for the end user to override, by just renaming items accordingly, to fit their cases best.

Looking forward to testing/evaluating further improvements on URI matching, and great work (so far)!

Hey folks, we've just posted an update about the future of these improvements so you're aware of what to expect in the coming months. Always happy to hear your feedback and answer any questions you might have :)

Gabriele

Our latest implementation uses a scoring system to determine how close of a match each item's URL is to the URL of the page you're visiting. Beyond that, items with the same score are sorted by their internal ID. That's probably why you're seeing them show up in a not so logical order in your list.

Are the accounts you're looking at all originating from the same website? What makes their ordering important to you?

Sorry, one more doubt: I don't know if it is related to this new feature, but I don't understand in what order the logins are proposed when there is more than one.
For a certain address I have 6 logins:
Account 1 (mail1@mail.com)
Account 2 (mail2@mail.com)
Account 3 (mail3@mail.com)
and so on
1Password however puts them in an order I don't understand (account 3 - 4 - 2 - 5 - 1 - 6). What is the sorting criteria for the logins? Thank you!

That won't be possible for the time being, but it's something we might consider in the future :)

Cheers,
Gabriele