Currently, when the autofill mode is set to Base Domain
, Bitwarden displays logins for different subdomains and services on various ports in an arbitrary order. This makes it inconvenient to quickly find the most relevant match.
For instance, when visiting blog.example.com
, the autofill suggestions might appear as: map.example.com
, bank.example.com
, and finally blog.example.com
.
Switching to the stricter Host
autofill mode may seem like a solution, as it prioritizes the exact match at the top of the list. However, this approach falls short for websites like google.com
, where most subdomains share the same set of credentials. In this case, logins for myaccount.google.com
would not appear when visiting mail.google.com
, making this mode a bit impractical (at least to users that are used to the Base Domain
mode).
To overcome these inconveniences, I would love to see a mechanism that allows users to customize how autofill suggestions are sorted, based on factors like:
- Levenshtein distance between the login entry’s
name
and the visiting page’shost:port
- Levenshtein distance between the login entry’s
URI
and the visiting page’shost:port
- Last used (autofilled) time of the login entry
- And more rules that I couldn’t think of at the moment, but people might find them useful…
Additionally, offering advanced users the option to write custom comparison functions in a secure, sandboxed environment would be extremely useful. Without such a feature, the only workaround is to clone and rebuild the extension/app, which is far from convenient.