Improve locked vault browser workflow

This commit is contained in:
Joe Julian
2026-04-23 20:37:49 -07:00
parent 4afbc3c933
commit d60a8d2fbf
5 changed files with 69 additions and 4 deletions
+19
View File
@@ -115,6 +115,25 @@ Expected behavior:
- custom URL fields such as `URL1`, `URL2`, and similar KeePass-style URL
slots
## Locked Vault Workflow
User story:
- When the current page has a login form but KeePassGO is locked, the browser
must still make that state visible on the page and in the popup.
- Unlocking KeePassGO should not require the user to reopen the popup multiple
times or reload the page before the extension becomes usable again.
Expected behavior:
- The popup shows a locked-state message instead of silently falling back to
"no matches."
- The inline page affordance stays visible on login forms while KeePassGO is
locked and tells the user to unlock the vault.
- After the vault is unlocked, the extension rechecks the page automatically
and turns the locked affordance back into live matches without requiring a
page reload.
For extension-side regression checks, run:
```bash