[CfT] Fix CfT specific policy path on Windows https://crrev.com/c/5008236 introduced Chrome for Testing specific policy path that is different from both Chrome and Chromium policy paths, however, that change only affects Linux build while the Windows CfT build still uses Chromium policy path in registry. This CL changes policy path CfT uses on Windows to SOFTWARE\Policies\Google\Chrome for Testing Bug: 326275044 Change-Id: I0eea603b88781e0f96dbab024c83a3fa2236ed5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5315959 Commit-Queue: Peter Kvitek <kvitekp@chromium.org> Reviewed-by: Yann Dago <ydago@chromium.org> Cr-Commit-Position: refs/heads/main@{#1264621}
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.