Don't default save card fix flow detection bits on iOS.

Before this CL, detected values on credit card form submission were
always set with `DetectedValue:USER_PROVIDED_NAME` and
`DetectedValue:USER_PROVIDED_EXPIRATION_DATE` bits on iOS. Presence
of these bits impacted `AutofillMetrics::CardUploadDecisionMetric`
indicating fix flow is always present. The detected values are passed
in the payments server request while uploading the card.
However CreditCardSaveManager's `should_request_name_from_user_` &
`should_request_expiration_date_from_user_` were always set to false.
This worked on iOS since fix flow is not a separate flow step. If user
has submitted a form with missing data, the save card infobar modal
lets user enter the data in the modal itself.

After this CL, `DetectedValue` bits would only be set if
cardholder name or valid expiry date is missing AND a save card modal
will be offered to collect them. CreditCardSaveManager's
`should_request_name_from_user_` &
`should_request_expiration_date_from_user_` won’t be defaulted to
false. This is needed to support Save Card Bottomsheet experiment on
iOS which will be shown when fix flow is not detected. Save card modal
will be shown when fix flow is detected.
`AutofillMetrics::CardUploadDecisionMetric` will have fix flow bits
set only when data is missing during form submission. Same for the
`DetectedValue` bits received by the payments server request.

A kill-switch flag `kAutofillDisableDefaultSaveCardFixFlowDetection`
has been added for the change affecting DetectedValue bits.

Followup CL updates existing fix flow detection tests in
CreditCardSaveManagerTest disabled for iOS and adds iOS-specific tests.

Bug: 391930098
Change-Id: Ib8717c8b234652abbbb2f919262627aaeeae82a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6238383
Commit-Queue: Kavita Soni <kavitasoni@chromium.org>
Reviewed-by: Siyu An <siyua@chromium.org>
Reviewed-by: Slobodan Pejic <slobodan@chromium.org>
Reviewed-by: Olivia Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/main@{#1425975}
9 files changed
tree: d5b7683076beddd09637c5991cc6bc54f97e999b
  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.