| commit | 71a0dbd6672e2ccb6d1008376cbb7acd315cb8d6 | [log] [tgz] |
|---|---|---|
| author | Justin DeWitt <dewittj@chromium.org> | Mon Dec 08 20:35:33 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 08 20:35:33 2025 |
| tree | 620c5a52fe9db1ce349d06b9e10614311ec3fdd7 | |
| parent | e26fab6af60509cc75fc66181910dea056530810 [diff] |
[M143] Use IsMultiInstanceEnabled in IsUnifiedFreEnabled. Original change's description: > Use IsMultiInstanceEnabled in IsUnifiedFreEnabled. > > This change makes IsUnifiedFreEnabled() use the helper function > IsMultiInstanceEnabled() to check for multi-instance support, ensuring > consistency with other multi-instance checks (such as the sync multi > instance deployment flag). > > Change-Id: I2376f5a5d6db478e204cec4dd0cc17708064d275 > Bug: b:462434467 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7178962 > Reviewed-by: Anthony Cui <cuianthony@chromium.org> > Reviewed-by: Michelle Abreo <michelleabreo@google.com> > Commit-Queue: Justin DeWitt <dewittj@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1547976} (cherry picked from commit 909da8aa8991edbe014b6a258bf0ba0b3cfb7a73) Bug: 462469170,b:462434467 Change-Id: I2376f5a5d6db478e204cec4dd0cc17708064d275 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7232700 Auto-Submit: Chrome Cherry Picker <chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com> Reviewed-by: Trevor Perrier <perrier@chromium.org> Commit-Queue: Srinivas Sista <srinivassista@chromium.org> Reviewed-by: Srinivas Sista <srinivassista@chromium.org> Cr-Commit-Position: refs/branch-heads/7499@{#3142} Cr-Branched-From: b30439823e5177773584139e72e0593e36863899-refs/heads/main@{#1536371}
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.