| Code-Review | +1 |
if (_autofillAISaveEntityCoordinator) {
[_autofillAISaveEntityCoordinator stop];
}Is this change necessary? `[_autofillAISaveEntityCoordinator stop];` already does nothing if `_autofillAISaveEntityCoordinator` is nil.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (_autofillAISaveEntityCoordinator) {
[_autofillAISaveEntityCoordinator stop];
}Is this change necessary? `[_autofillAISaveEntityCoordinator stop];` already does nothing if `_autofillAISaveEntityCoordinator` is nil.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS] CloseEntityImportBubble should close the entity import bottomsheet
Here's the call flow:
1. Once the user accepts the save bubble, if it is a synchronous bubble,
the entity is saved right away and the bottomsheet is closed.
2. If the save is asynchronous, the view shows the loading state and
the callback is run.
3. AutofillAiManager::HandlePromptResult does the api call from the
client.
4. Once the response is received, HandleWalletUpsertResponse is called
which depending on the response on api call, calls either
`ShowAutofillAiLocalSaveNotification` or the error method
`ShowAutofillAiSaveToWalletFailureNotification`
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |