Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
steve28
3 years agoOccasional Contributor
Autofill... domain matching choices?!? O. M. G.
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
- TertiusSuper Contributor
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. - roustem
1Password Team
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.
- TertiusSuper Contributor
@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.
- Former Member
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 :)