
This class is very similar to the C++ NetworkTrafficAnnotationTag class. It requires the same kind of documentation, in as a text protobuf. As a proof-of-concept, update EndpointFetcher methods to take a NetworkTrafficAnnotationTag argument, and plumb it down to C++. For now, use NO_TRAFFIC_ANNOTATION_YET in callers. Since auditor.py doesn't scan Java files yet, the contents of the annotations doesn't need to be valid for now. Bug: 1231780, 995852 Change-Id: I798a99adfd9d2d2afee537b78d379e9f05b49a9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3045770 Reviewed-by: David Trainor <dtrainor@chromium.org> Reviewed-by: Ryan Sleevi <rsleevi@chromium.org> Reviewed-by: Andrew Grieve <agrieve@chromium.org> Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by: Ramin Halavati <rhalavati@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/main@{#917776}
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.