Holy crap. It's here! Mostly! It would be awesome if you had ONE more choice: domain only: match as long as domain.com matched host: the full host needs to match (i.e., sub.domain.com) full URL: the full host, port, and path 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Browser:_ Not Provided

Great idea, steve28 ! +1 vote from me 👍

Hi steve28, glad you noticed the changes :) I’m one of the designers behind this feature and it’s part of a bigger set of changes to coming to Autofill. Currently we only support the “default” behavior (loose matching), strict matching by host (whole host including subdomains must match exactly) and “never” which causes the item to never show as a suggestion on the specified URL. We’re working on an overhaul to the algorithm used for Autofill suggestions which might help address your other concerns. We’ve made it so that the suggestions now take into account the path, the subdomain, the port and scheme in order to boost the most fitting suggestions. This update to the algorithm is still a work in progress and disabled by default. It can be enabled in the betas, under Autofill settings in the extension and under advanced settings in the desktop app. Enabling in on both will give you consistent suggestions across the extension and the desktop app as a nice bonus :) Please be warned that these features are experimental and not ready for prime time. There’s no risk to testing them out but you’ll probably run into bugs like duplicated suggestions or suggestions for items you’ve archived or recently deleted. We’re ironing those out. As long as you don’t depend on these features for your daily work, or just want to give them a 15-minute try, feel free to give them a shot and report on your thoughts :)

@ag_Gabriele I'm using them in the beta plugin, and I notice one annoying thing has vanished: a favorited but not exactly matching entry was shown above a perfectly matching (including subdomain) but non-favorited entry. Now the perfectly matching entry is the first offered choice. This is the way it should be.

This is the way it should be. Huh, I just came here to complain that the new matching algorithm completely broke my workflows for Google and Amazon where I have close to 200+ logins combined. I now see logins that I would use maybe once a year showing at the top of the list. I used to manually mark a few items as favourites and they always showed on top.

To elaborate what I find good: I have a favorited entry for www.somedomain.de. I have another non-favorited entry for hostname.home.somedomain.de. I request hostname.home.somedomain.de with my browser, and previously, I was offered both entries with the favorited one on top for login. That was clearly wrong, since the second one was a better match. Now, with the different matching algorithm I was offered the second entry first, and that's what I wanted in the first place. However, I also set the second entry to "only fill on this exact domain" in the website details of the 1password login entry. Dunno which setting actually made the change - the configuration in the item or the global plugin configuration setting.

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

Former Member
3 years ago
DenalB thanks for the feedback. Just thinking through this, I wonder if those two things would be mutually exclusive in your perception? I.e. are there situations where a hypothetical "don't show suggestions on this website" option would be useful and where the existing "Never fill on this website" wouldn't, or vice versa? For example one scenario I can think of is a website where you don't want some suggestions but not all. Whereas on some other sites (or maybe specific pages?), as you say, you might want to disable suggestions altogether. Curious about your thoughts.
DenalB
Super Contributor
3 years ago
@ag_Gabriele
Instead of having a setting Never fill on this website in every login entry, it would be much better to decide on specific websites not to show any suggestions, like a blacklist or something. And I know that there is a long-awaited feature request for the extension, already. 😉
Tertius
Super Contributor
3 years ago
@robochacho Websites tend to change their hostname part. Often it is "www.somewebsite.com", but sometimes "www1.somewebsite.com" and more digits 1..9, "login.somewebsite.com", or just "somewebsite.com", or whatever prefix their admins choose. This prefix is changed now and then during the lifetime of the website, invisible to the user, so I feel the default ("fill anywhere") is just right - it ignores any prefix and matches just *.somewebsite.com. Otherwise, 1Password would just stop offering autofill if the prefix is changed behind the scenes, and you are suddenly locked out until you manually find that entry and correct it.

If you really have some website where you must match even the hostname part, you can change the matching. However, that's usually not the vast majority of entries.
Former Member
3 years ago
@robochacho happy to hear! Let us know about your experience with these new features.

We haven't looked into allowing you to set a global default, however we'd like to hear more about bulk use-cases and see what we can do to help with that. Can you tell us more about the nature of the logins you'd be editing? I imagine the "only fill on this exact domain" behavior is only useful in certain situations, so would it make more sense to you to have a global default or a way to change specific items in bulk?
Former Member
3 years ago
I'm trialing 1Password over a competitor and you have me as an instant customer if the new autofill features work well.

Question - will we have the ability to set a global default autofill behavior? Editing hundreds of logins sounds miserable or am I overlooking something?
Former Member
3 years ago
Lovely! If you have any questions or feedback we're always here to listen.

Cheers,
Gab
DenalB
Super Contributor
3 years ago
Hey @ag_Gabriele !

Hope you get to try the setting again in the next beta, and let us know how it feels.
I'll do so. 😉

Those known issues should most likely be fixed then.
I'm looking forward to these fixes.
Former Member
3 years ago
DenalB apologies, “never”’s actually only found in the nightly for now. If you’re on windows, you also won’t see the new setting under “advanced” because that’s part of the Universal Autofill feature found on the macOS version only. It’s not currently available on windows because we don’t have the ability to support Universal Autofill there. By using the browser extension, you should get most of the mileage out of this feature.

Hope you get to try the setting again in the next beta, and let us know how it feels. Those known issues should most likely be fixed then.

Gabriele
DenalB
Super Contributor
3 years ago
Hey @ag_Gabriele !

and “never” which causes the item to never show as a suggestion on the specified URL
Sounds good. But I don't have a setting for "never". I'm using 1Password for Windows 8.9.11 (80911014).

It can be enabled in the betas, under Autofill settings in the extension and under advanced settings in the desktop app.
I have this setting in 1Password for Firefox beta 2.6.1, but not in 1Password for Windows 8.9.11 (80911014).

Maybe this setting appears in the next beta build for Windows. 😉

There’s no risk to testing them out but you’ll probably run into bugs like duplicated suggestions or suggestions for items you’ve archived or recently deleted.
That's what I recognized already, and that's why I disabled the setting in the browser extension after trying for a day. 😊
https://1password.community/discussion/135868/setting-improved-autofill-suggestions-what-does-it-mean
Former Member
3 years ago
Both changes probably helped in different ways. Setting something to “only fill on this exact domain” won’t affect how it ranks in suggestions, just whether it displays or not. Although adding this as an extra signal to the ranking algorithm is something that might be worth considering.