Remove completed browser extension todo items
This commit is contained in:
@@ -46,15 +46,6 @@ feeling like the same application rather than three related UIs.
|
|||||||
These should remain in the main user flow rather than being hidden behind a settings gear.
|
These should remain in the main user flow rather than being hidden behind a settings gear.
|
||||||
|
|
||||||
- Browser extension:
|
- Browser extension:
|
||||||
make browser autofill page-driven rather than popup-driven so the user does not need to manually open the extension to discover or use matches.
|
|
||||||
- Browser extension:
|
|
||||||
add per-page or per-tab match detection and visible state so the browser can indicate when KeePassGO has a candidate for the current login form.
|
|
||||||
- Browser extension:
|
|
||||||
persist page match state so opening the extension popup is not required multiple times for the same page and does not repeat the whole discovery workflow unnecessarily.
|
|
||||||
- Browser extension:
|
|
||||||
show inline field affordances on detected username and password inputs, with a candidate chooser anchored to the field, so browser autofill is selectable from the form itself like Android autofill.
|
|
||||||
- Browser extension:
|
|
||||||
treat missing visibility of a pending authorization request during browser autofill as a workflow failure and fix approval surfacing before expanding extension scope further.
|
|
||||||
- Local open flow:
|
- Local open flow:
|
||||||
make the start screen primarily about opening a vault, not configuring one.
|
make the start screen primarily about opening a vault, not configuring one.
|
||||||
- Local open flow:
|
- Local open flow:
|
||||||
|
|||||||
Reference in New Issue
Block a user