Deprecate import logic for incomplete profiles

Upon form submission, FormDataImporter extracts an AutofillProfile from
the submitted FormStructure. If at least one profile is found,
AutofillProfileImportProcess is asked to determine the import type, by
looking at existing profiles, strikes, etc. This is represented by
AutofillProfileImportType.

After FormDataImporter extracted a profile, it determines if the profile
meets Autofill's completeness requirements [1]. This CL's main
observation is that incomplete profiles are dropped. Yet, a few lines
after the early return, ExtractedAddressProfile has a
all_requirements_fulfilled property, that consequently is always true.
This CL removes all dead code around incomplete imports.

In the import process the import types kSilentUpdateForIncompleteProfile
and kUnusableIncompleteProfile are meant to deal with incomplete
imports. According to metrics [2], both are dead. However, looking at
the code, it appears that they can be triggered through a rarely
occurring special case:
- If FormDataImporter cannot show a prompt (e.g. because a credit card
  import is possible), it attempts to perform silent updates only [3].
  In this case, kNewProfile/kConfirmableMerge import types are converted
  to kUnusableIncompleteProfile/kSilentUpdateForIncompleteProfile [4].
  This seems semantically wrong.
To remove the two incomplete profile import types, this CL instead
treats the case above as kSuppressedNewProfile and
kSuppressedConfirmableMerge.

[1] https://source.chromium.org/chromium/chromium/src/+/main:components/autofill/core/browser/form_import/form_data_importer.cc;l=715-716,740-742;drc=43cfaa57fbbef87d4daa61e8c707326dea4efe7c
[2] https://uma.googleplex.com/p/chrome/timeline_v2?sid=51c6e1a3404976e1ebbedfa974b4d47b
[3] https://source.chromium.org/chromium/chromium/src/+/main:components/autofill/core/browser/form_import/form_data_importer.cc;l=784,802;drc=43cfaa57fbbef87d4daa61e8c707326dea4efe7c
[4] https://source.chromium.org/chromium/chromium/src/+/main:components/autofill/core/browser/form_import/addresses/autofill_profile_import_process.cc;l=219,235-239;drc=30382c187a4dadbd3624660808311c4da276f888

Bug: 354706653, 40100455
Change-Id: Ie73719ea91b0c0a5b5e8ad303724c2bedcbbd95f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6656471
Reviewed-by: Piotr Kotynia <piotrkotynia@google.com>
Reviewed-by: Dominic Battré <battre@chromium.org>
Commit-Queue: Florian Leimgruber <fleimgruber@google.com>
Cr-Commit-Position: refs/heads/main@{#1481468}
8 files changed
tree: c148df903a6591bd1891e995b920d163b2c301ad
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  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. .cursorignore
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. 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.