| commit | c7ac344237d0760c3e7d1361c456977050353263 | [log] [tgz] |
|---|---|---|
| author | Daniel Rubery <drubery@chromium.org> | Mon Oct 09 22:16:20 2023 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 09 22:16:20 2023 |
| tree | acc0975f8c428685ce33baf8ebc92376edcd9e55 | |
| parent | 6dba28d9a5defc5b7ce65e19b19ee94655947b04 [diff] |
Add security FAQ entry about file type bugs We're much less interested in these bugs than we used to be. It's nice to have some documentation to point to as to why. Change-Id: I2ef2d3c7ba6a7092489ddb86834581e3e6443ce7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4923529 Reviewed-by: Adrian Taylor <adetaylor@google.com> Commit-Queue: Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/main@{#1207331}
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.