Make it easier to load a configuration via the domain input field.

200ms after the last character entered, a background domain search will run to determine if a configuration exists for a variation of the current entered domain (adding typically used subdomain prefixes and TLDs).

If found, a suggestion is displayed that can be picked by pressing TAB.

This makes it easier to load configurations if you are unsure about the exact domain the configuration was generated for, e.g. when a website changed it's login (sub-) domain.

Because of the way configurations are stored (for security and privacy reason), this can in rare cases show false positives and display a domain (that often won't make sense) that you don't actually have a configuration for. This is not a bug or a signal you were hacked, just a side effect of the configuration storage mechanism.

Fix a UI regression in 1.5.0.

You were no longer able to create configurations for new domains.

TOTP secrets can now be saved per-domain to generate one-time passwords directly in the extension.

The feature is fully optional: if you don't configure a TOTP secret for a domain, nothing changes about the existing password derivation flow.

Because TOTP codes can't be derived from a master password, their secrets must be stored to disk; they are encrypted (XOR against the per-domain HKDF key) and are included in configuration backups, use of which will be recommended if you use this feature.