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) ...
Former Member
3 years agoHi! (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)!