commit | 5052822fa73d97ba135bb3eb15282ae3371cc662 | [log] [tgz] |
---|---|---|
author | Clemens Arbesser <arbesser@google.com> | Mon May 10 11:23:04 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 10 11:23:04 2021 |
tree | e92994a8bc02d70d0fe82566768f5f15cfd92857 | |
parent | 632e3e20def08b3c47a11a3a48021a1d3758ec6e [diff] |
[Autofill Assistant] Split in-Chrome triggering feature. This will allow us to ramp in-CCT triggering and in-Tab triggering independently of each other, and have separate launches for each of them. Bug: b/185326469 Change-Id: I662b712287ff6cad78ff282de6d23d118a9487f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2864023 Commit-Queue: Clemens Arbesser <arbesser@google.com> Reviewed-by: Sandro Maggi <sandromaggi@google.com> Cr-Commit-Position: refs/heads/master@{#880916}
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.