Update FormTracker using blink form mutation signal.

Previously Autofill used to use a WebFormElementObserver in order to
track elements disappearing for submission detection purposes.

E.g. When XHR happens, if the tracked element had disappeared by then,
we infer form submission, but if the element disappears later we would
need another mechanism to check that. This observer was the needed mechanism.

Given that this was not strong enough as a signal to detect hidden
elements (only detects display: none) a signal was introduced in a prior
CL from blink to Autofill for when elements are added, removed or
hidden.

In this CL, we use the kRemoved and kHide signals to inform FormTracker
that maybe the tracked element disappeared, and in that case,
FormTracker can maybe infer form submission.

The observer was used for 3 cases:
- XHR, then tracked element disappeared.
- Same document navigation, then tracked element disappeared.
- (PWM only) Autofilled element then tracked element disappeared.

This CL therefore introduces 4 booleans representing each one of those
cases + a boolean that tracks if the tracked element disappeared or not.
This way we only infer submission for event X if both event_x_happened
and tracked_element_disappeared booleans are set to true.

This CL also disables the use of the observer.

Lastly, the CL drops the form extraction done in GetSubmittedForm, as
this would cause problems when called from within a style recalc in
blink. Instead, it uses `provisionally_saved_form_` unconditionally
and so the submitted form would be the version of the form last edited
by the user.

When the introduced feature is disabled, this CL is a no-op. All changes described previously are gated by the added feature flag.

Bug: 1483242
Change-Id: Ib1793841a8a0dbf8bc3dff3244cce82809e00853
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5041251
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Jihad Hanna <jihadghanna@google.com>
Reviewed-by: Christoph Schwering <schwering@google.com>
Auto-Submit: Jihad Hanna <jihadghanna@google.com>
Cr-Commit-Position: refs/heads/main@{#1271468}
10 files changed
tree: 4ec34bd413b3c64b2252094da9b92c4c3f75a13c
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  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. 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.