Google Git
Sign in
chromium / chromium / src / d4c2e9a5e51331b28ce898d1cc8d964846b5cfae
commitd4c2e9a5e51331b28ce898d1cc8d964846b5cfae[log] [tgz]
authorChristoph Schwering <schwering@google.com>Thu Sep 15 14:23:54 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Sep 15 14:23:54 2022
tree598d96e4b4ec85fc804afc600b9e971466175371
parent8b491da9bb7cb9f44bf9ad36406873e0a107d1b3 [diff]
Reland "Reland: "[Autofill] Enable AutofillParseAsync in some tests.""

This is a reland of commit 478833e0f3dfdbffd01f0587e8a84e03e9d85aeb

Original change's description:
> Reland: "[Autofill] Enable AutofillParseAsync in some tests."
>
> This is a reland of commit 9c6e7a6c7b469cca490868424ff287403f47b972.
>
> The CL broke tests in autofill_browsertest.cc and
> autofill_manager_unittest.cc. Fixes of these tests landed in
> crrev.com/c/3888165, crrev.com/c/3888166.
>
> Original change's description:
> > This CL adds a fieldtrial testing config for asynchronous form parsing
> > and enables the feature in several unit tests.
> >
> > Bug: 1309848, 1345089
> > Change-Id: I1c2efe9aff6ab61d05b2316e3673e574aaf2f9ae
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3798546
> > Commit-Queue: Christoph Schwering <schwering@google.com>
> > Reviewed-by: Florian Leimgruber <fleimgruber@google.com>
> > Cr-Commit-Position: refs/heads/main@{#1042851}
>
> Bug: 1309848, 1345089
> Change-Id: I70ba79c3b0a88d56513f6d4362f5d308ceecfe91
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3870617
> Commit-Queue: Christoph Schwering <schwering@google.com>
> Reviewed-by: Florian Leimgruber <fleimgruber@google.com>
> Cr-Commit-Position: refs/heads/main@{#1046040}

Bug: 1309848, 1345089
Change-Id: I1ce561e9823810252cefad84b258961c03441a7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3894672
Commit-Queue: Christoph Schwering <schwering@google.com>
Auto-Submit: Christoph Schwering <schwering@google.com>
Reviewed-by: Florian Leimgruber <fleimgruber@google.com>
Cr-Commit-Position: refs/heads/main@{#1047466}
10 files changed
tree: 598d96e4b4ec85fc804afc600b9e971466175371
  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. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.