GitLab

Since we're planning to launch the same editing activity in two
different cases, a new generic interface for launching the editing
activity and saving the changes on passwords has been added. It's called
password_change_delegate. Two different delegates will implement it in
two possible use cases.

In the first use case the editing activity is launched from the password
viewing activity or from the password list displayed in the saved
password preferences. In that case the password entry already exists in
the store and needs to be changed.

In the second use case the editing activity is launched from the InfoBar
when a new password was detected and still hasn't been saved in the
store. In that case, another delegate will implement the interface and
it will have to create new password records in the store.

Because we can't rely on PasswordManagerPresenter persisting through the
process, the delegate and the PasswordEntryBridge need to stay alive
while the password editing activity exists. They need to be destroyed
when the password editing activity is destroyed.

Bug: 377410
Change-Id: I53be371375a590c9b928e98800b0be24a36f333d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768524Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Friedrich [CET] <fhorschig@chromium.org>
Commit-Queue: Ivana Zuzic <izuzic@google.com>
Cr-Commit-Position: refs/heads/master@{#691602}