-
Notifications
You must be signed in to change notification settings - Fork 46
Autofill Extension (iOS 12) #486
Comments
Related bugzilla 🐛 for Firefox iOS work (P2, prioritized for version 13.0): |
@nickbrandt we'll need to provide coverage for two additional screen states:
@sashei will we also need to handle any other instances where enabling Lockbox fails... and if so, will we know what has failed to be able to provide context? Additionally, please correct me if I've not addressed something as we had discussed. |
@changecourse I think not being authenticated is the the main case to handle, I will update y'all if I discover anything else. |
@changecourse I am breaking this down into engineering tasks, the associated stories for the convo / summary above are #611 & #612 |
@sandysage will review this and "convert" it to an epic, make sure all stories are accounted for as well. |
This story is now an epic. I added a couple of new items to account for telemetry and FAQ updates. @sashei Do we need any stories around providing autofill setup from settings? Am I overlooking that? @nickbrandt I'm not finding any flows for when no match is found in the Credential List. How is that being handled? I think we noted that we should display all options with some ability to search/filter but without going to details or settings from within this list view. Am I just overlooking it in in Invision? |
@sandysage When going to the credential list (tapping the key), the idea is that the associated domain with whatever login screen they were coming from would be prefilled in the search bar (as seen here: https://mozilla.invisionapp.com/share/RWEHBJQH9#/304302923_AutoFill_-_App_Example_-_Credential_List). If this results in no matches found, we would present them with the same screen we did for the No Matches state in the app. From there they can clear out the search field (domain), and select a different entry if they wish. I will create an additional screen to showcase this state though. |
@sandysage showing the option to enable Autofill in settings should be taken care of by #622. There are two set-up stories related to Settings enablement, #611 and #612. |
@nickbrandt @sashei thank y'all! I think I'm set here. |
Closing this with two acceptance criteria no longer complete:
|
Follow up to #476 exploration
This is an epic where we want to capture the consolidated design/user stuff for the autofill feature, we may split out to separate engineering stories as needed.
-
ASCredentialIdentityStore
to store and update dataDesigns
InVision
Onboarding Flow to Settings
https://mozilla.invisionapp.com/share/BQEUSO0S2#/316626649_AutoFill_-_Onboarding
Example App Flow for AutoFill
https://mozilla.invisionapp.com/share/BQEUSO0S2#/316626653_AutoFill_-_App_Example
Epic
ASCredentialIdentityStore
when enabling Lockbox as an autofill credential provider #612ASCredentialIdentityStore
after authenticating if Lockbox is already enabled as an autofill credential provider #613ASCredentialIdentityStore
#614Acceptance Criteria
[ ] Should have the ability to set specific Lockbox autofill settings (ex: quicktype bar suggestions) - this is a big maybe and requires some explorationThe text was updated successfully, but these errors were encountered: