Google Git
Sign in
chromium / chromium / src / d8d8387e57b2f47982e94047771a3027833e30db
commitd8d8387e57b2f47982e94047771a3027833e30db[log] [tgz]
authorTakashi Sakamoto <tasak@google.com>Tue Sep 24 02:12:37 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Sep 24 02:12:37 2024
tree1af905dbeed5ccd859ad5cdd92bd53de6271796a
parente0558c1de471e057cd8526927f7f1bd27e30f075 [diff]
Revert "Enable AutofillUnifyAndFixFormTracking by default"

This reverts commit 48b1dd871ad658ab9f029eea11074b1b1d34d92a.

Reason for revert: suspect browser_tests failure on linux-chromeos-chrome, linux-win-cross-rel, ...

browser_tests failed because of:
PasswordManagerBrowserTest.IFrameDetachedRightAfterFormSubmission_UpdateBubbleShown

First build failure:
https://ci.chromium.org/ui/p/chrome/builders/ci/linux-chromeos-chrome/45032/
https://ci.chromium.org/ui/p/chromium/builders/ci/Win10%20Tests%20x64/94065/
https://ci.chromium.org/ui/p/chromium/builders/ci/linux-win-cross-rel/2578/
 
Original change's description:
> Enable AutofillUnifyAndFixFormTracking by default
>
> Bug: 40281981
> Change-Id: I5d4832bf468fdbcc36968d42fa06a3077ff97ace
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5880876
> Reviewed-by: Olivia Saul <jsaul@google.com>
> Reviewed-by: Dominic Battré <battre@chromium.org>
> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
> Commit-Queue: Jihad Hanna <jihadghanna@google.com>
> Cr-Commit-Position: refs/heads/main@{#1359005}

Bug: 40281981
Change-Id: Id146c42f84b21fe587107d691b56bb3f34298e7b
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5883160
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Takashi Sakamoto <tasak@google.com>
Owners-Override: Takashi Sakamoto <tasak@google.com>
Cr-Commit-Position: refs/heads/main@{#1359144}
8 files changed
tree: 1af905dbeed5ccd859ad5cdd92bd53de6271796a
  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. google_update/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. clank
  51. internal
  52. ios_internal
  53. native_client
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .eslintrc.js
  60. .git-blame-ignore-revs
  61. .gitallowed
  62. .gitattributes
  63. .gitignore
  64. .gitmodules
  65. .gn
  66. .mailmap
  67. .rustfmt.toml
  68. .vpython3
  69. .yapfignore
  70. ATL_OWNERS
  71. AUTHORS
  72. BUILD.gn
  73. CODE_OF_CONDUCT.md
  74. codereview.settings
  75. CPPLINT.cfg
  76. CRYPTO_OWNERS
  77. DEPS
  78. DIR_METADATA
  79. LICENSE
  80. LICENSE.chromium_os
  81. OWNERS
  82. PRESUBMIT.py
  83. PRESUBMIT_test.py
  84. PRESUBMIT_test_mocks.py
  85. README.md
  86. 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.