1. Remove |kEnableUsernameCorrection| and |kEnablePasswordSelection| flags as the corresponding features are stabilized.
2. Introduce |is_update_bubble| flag to |ManagePasswordsBubbleView::PendingView|. Merge the code of |PendingView| and |UpdatePendingView| into |PendingView|. I.e. simply use |if (is_update_bubble) { /* code for update case*/} else { /* code for save case */}|.
3. Make username editable for update cases when there is only one credential (i.e. |CredentialsSelectionView| is not needed).
4. Introduce the password selector and the eye icon for update cases.
5. Update the backend logic, if needed.
6. Implement an editable combobox for the password selector.
7. Introduce an editable username selector that is available for both save and update cases.
8. Decide whether we should change title and buttons if username editing switches the state from save to update or back?
9. Move the eye icon inside the password selector (aka ZigZag problem).
1. Remove |kEnableUsernameCorrection| and |kEnablePasswordSelection| flags as the corresponding features are stabilized.
2. Introduce |is_update_bubble| flag to |ManagePasswordsBubbleView::PendingView|. Merge the code of |PendingView| and |UpdatePendingView| into |PendingView|. I.e. simply use |if (is_update_bubble) { /* code for update case*/} else { /* code for save case */}|.
3. Make username editable for update cases when there is only one credential (i.e. |CredentialsSelectionView| is not needed).
4. Introduce the password selector and the eye icon for update cases.
5. Update the backend logic, if needed.
6. Implement an editable combobox for the password selector.
7. Introduce an editable username selector that is available for both save and update cases.
8. Decide whether we should change title and buttons if username editing switches the state from save to update or back?
9. Move the eye icon inside the password selector (aka ZigZag problem).
10. Add metrics.
11. Add tests for views
Comment 1 by kolos@chromium.org
, Jan 9 2018