[fedcm] Autofill emails only if the user accepts the modal dialog prompt

For verified email addresses, we'll show the FedCM modal dialog to get
some confirmation that the user wants to share their email address
(along with other fields, such as names and profile pictures).

When the modal dialog is shown, the user has the choice to reject or
dismiss it. When that happens, we want to make sure that the field does
not get auto-filled (in addition to failing the promise of the
conditional request).

For the password field recommendation, on the other hand, a modal isn't
necessary, and the token can be auto-granted without requiring extra
prompting.

To accomplish these differences, we introduce:

- A boolean parameter to OnFederatedTokenReceivedCallback, to let the
  browser and password autofill managers know if the request succeeded
- A boolean autogrant parameter to NotifyAutofillSuggestionAccepted to
  let the FederatedAuthAutofillSource know whether to request
  additional permission or not

And the necessary implementation in the FederatedAuthAutofillSource to
accomplish the semantics described above.

Bug: 380367784
Change-Id: I8f5bf5d75738ad0f6e1d2545ecc8f2697cfe8806
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6484645
Commit-Queue: Sam Goto <goto@chromium.org>
Auto-Submit: Sam Goto <goto@chromium.org>
Reviewed-by: Jihad Hanna <jihadghanna@google.com>
Cr-Commit-Position: refs/heads/main@{#1453194}
12 files changed
tree: b327cce814644ac32583aab77fe25f60cff699c4
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

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.