[webauthn] Fix favicons not showing on autofill If webauthn credentials were the only available credentials on the device (i.e. there were no passwords saved), then PasswordAutofillManager::OnAddPasswordFillData was never called. This in turn meant that RequestFavicon was not called, so the favicon was empty. This CL changes the behaviour to have ContentPasswordManagerDriver::SetPasswordFillData call PasswordAutofillManager::OnAddPasswordFillData even if the fill data is empty, and havePasswordAutofillManager::OnAddPasswordFillData explicitly check for that case so it has a chance to request a favicon. Fixed: 1370037 Change-Id: I679d39b06e40b9bb11238b65397207adc398ae25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3932362 Auto-Submit: Nina Satragno <nsatragno@chromium.org> Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1055211}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.