Currently, when opening bitwarden to fill a credential, the credentials do not appear to sort based on how the URL match was done. That is, if I have 3 different entries for Amazon.com – two of them using base domain match and one using “begins with” to match aws.amazon.com-- the less specific matches may appear higher up in the list than the more specific one.
There are a number of situations where this can cause headaches (beyond the obvious example of sites like Amazon). Local state institutions frequently share base domains for different services that may have different credentials, and have different rules about what subdomains or URL paths are used for those services. It may be the case that across a half dozen credentials for a toplevel domain, you have 2 that work across base domain match, 3 that use “starts with”, and one or two for an exact match.
Ideally, when matching is done, URLs with a match rule of “exact match” would be grouped and sorted first, followed by “begins with”, followed by “regular expression”, then “host”, then “base domain”. Within those groups, entries with an exactly matching URL should come first (regardless of the specified match rule), followed by alphabetical ordering.
This will generally create a predictable and intuitive sorting. Sticking with the default domain match will still result in exact URL matches showing up first, and going out of your way to change the URL match will generally result in prioritized sorting.