Save new credentials from Autofill #217
Comments
I've done some more investigation, and I think we can avoid the |
onSaveRequest
as AutofillService
This is not a 'must have' for initial launch. It is something we need to provide prior to the Fenix launch to support our 'family of products' on Android |
@eliserichards looking back through this (for the first time since May) do you mind taking a stab at the questions I have above? That'll help me plan a design approach and unblock the issue. If not you, then perhaps @jhugman |
Commenting as QA Needed label is added. |
I was also able to save a login using Duolingo and 9gag app. |
@abodea Unfortunately that has been the case for the autofill feature too. It's something we're considering for how we improve the app going forward: 1. defining some set of sites/apps where autofill is not working 2. triage/scope these cases and 3. come up with a plan for getting all of autofill (both fill and capture) working in more places. I'll create a ticket specifically for that initial definition work. |
Verified as fixed on v.4.0.0(6016) using Google Pixel 3 XL(Android 9), Samsung Galaxy S10+(Android 9). |
Acceptance Criteria
Save credentials when the user enters credentials that we don't have in Lockbox. For now, this will not respect app locked state; that will be handled in a follow-up ticket #632 or saving values from multi-screen login experiences #633
Engineering notes
Handle the
onSaveRequest
callback.Todo
onSuccess
called inLockboxAutofillService
onFillRequest
-- documentationParsedStructure
to implementfindNodeById
getAutofillValues
+ map toServerPassword
DataStoreAction.Add(credential: ServerPassword)
DataStoreAction.Add
inDatastore.kt
Testing steps
The best way to test a successful save is to use the Duolingo app (it works 100% of the time)
The text was updated successfully, but these errors were encountered: