commit | c91bd8ea7952b09a97c509376dc9d4371cd359cc | [log] [tgz] |
---|---|---|
author | Avi Drissman <avi@chromium.org> | Mon Apr 19 23:58:44 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 19 23:58:44 2021 |
tree | 917d1bee80437795409b422bc34825b47cd65171 | |
parent | 9e4cf31c36e310e9636a5a16d322433f2523c9f8 [diff] |
Migrate to ExecJs/EvalJs in content/ Bug: 1157718 Change-Id: Ibb5bdb3f994630cc2b84f4e60adaf307fe646cb3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2826401 Auto-Submit: Avi Drissman <avi@chromium.org> Commit-Queue: John Abd-El-Malek <jam@chromium.org> Reviewed-by: John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#874039}
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.