commit | da502845e63e1ced3c6e41b9153a57b9af107baa | [log] [tgz] |
---|---|---|
author | Raphael Kubo da Costa <kubo@igalia.com> | Thu Jan 16 17:16:37 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 16 17:16:37 2025 |
tree | 377af396ff10fc36e9f54fbae21153e1ed56ea31 | |
parent | d4549485c89e9adca13a6c45035ceb9afd1f6587 [diff] |
embedder_support: Remove Windows-specific code path from ReduceUserAgentPlatformOsCpu test Having separate code paths made sense when we supported Windows < 10. Since https://crrev.com/c/4127097, the Windows and non-Windows code paths in the unit test are functionally equivalent (the "platform OS CPU" part of the Windows code path will always match what's in |kDesktop|). Change-Id: I57f707f04be922981d6e144a99185301baef50a5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6179697 Commit-Queue: Mike Taylor <miketaylr@chromium.org> Reviewed-by: Mike Taylor <miketaylr@chromium.org> Auto-Submit: Raphael Kubo da Costa <kubo@igalia.com> Cr-Commit-Position: refs/heads/main@{#1407371}
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.