[Autofill] Deep compare forms and fields when extracting forms

In this change, we introduce a new deep comparison function for FormData
and FormFieldData structs used when updating the FormCache.

The old ExtractNewForms() is responsible for extracting new and changed
forms in the DOM. It is called on page load or when a new field is added
(or called by TriggerReparse()). When called, it also re-extracts forms
that have other changes than having a new field.

This CL changes the behaviour of the kAutofillUseNewFormExtraction
experiment to have the same behaviour as the non-experimental
ExtractNewForms().

To this end, this CL introduces a DeepEqual() function for FormData and
FormFieldData. These functions compare *all* attributes. To improve
performance, they do a shallow comparison first. Preliminary testing
has shown that the shallow and deep comparisons differ in 4% of
comparisons; a metric is added in a followup CL.

To better reflect this behaviour of re-extracting not just new forms or
forms with new fields but all changed forms, this CL renames the
function to UpdateFormCache()

Bug: 1215333
Change-Id: I7af67bb485bdb28cd7b13bb6873c3d7e1462f749
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138805
Reviewed-by: Christoph Schwering <schwering@google.com>
Reviewed-by: Matthias Körber <koerber@google.com>
Commit-Queue: Eva Herencsárová <evih@google.com>
Cr-Commit-Position: refs/heads/main@{#922624}
8 files changed
tree: a7f8a9772b2abda26d85985810a356e8c202dec4
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  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.