Skip to content

Commit 5ba1486

Browse files
committed
Merge to M70: Update flag description for chrome://flags/#enable-site-per-process.
The "Disabled" value is legacy and confusing, since it actually means "Default" (which is currently "Enabled" on desktop platforms). Unfortunately, updating the label to "Default" would reset users' preferences, which is undesirable (especially on Android). Instead, update the description to clarify the meaning of the settings and to point to chrome://process-internals for checking status. Bug: 879633 Change-Id: I672f5ebe4ef75482493f0668b64d6d20144d15ed Reviewed-on: https://chromium-review.googlesource.com/1198011 Commit-Queue: Charlie Reis <[email protected]> Reviewed-by: Alex Moshchuk <[email protected]> Cr-Commit-Position: refs/heads/master@{#588098} Also merges r588601: Fix typo in enable-site-per-process flag description. Change-Id: Ia8d706326522a26505be7848b78fae396de99755 Reviewed-on: https://chromium-review.googlesource.com/1204732 Reviewed-by: Alex Moshchuk <[email protected]> Commit-Queue: Charlie Reis <[email protected]> Cr-Original-Commit-Position: refs/heads/master@{#588601} Reviewed-on: https://chromium-review.googlesource.com/1208950 Reviewed-by: Charlie Reis <[email protected]> Cr-Commit-Position: refs/branch-heads/3538@{#74} Cr-Branched-From: 79f7c91-refs/heads/master@{#587811}
1 parent 3d3d7a4 commit 5ba1486

File tree

1 file changed

+12
-6
lines changed

1 file changed

+12
-6
lines changed

chrome/browser/flag_descriptions.cc

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1738,15 +1738,21 @@ const char kSingleTabModeDescription[] =
17381738

17391739
const char kStrictSiteIsolationName[] = "Strict site isolation";
17401740
const char kStrictSiteIsolationDescription[] =
1741-
"Security mode that enables site isolation for all sites. When enabled, "
1742-
"each renderer process will contain pages from at most one site, using "
1743-
"out-of-process iframes when needed. When enabled, this flag forces the "
1744-
"strictest site isolation mode (SitePerProcess). When disabled, the site "
1745-
"isolation mode will be determined by enterprise policy or field trial.";
1741+
"Security mode that enables site isolation for all sites (SitePerProcess). "
1742+
"In this mode, each renderer process will contain pages from at most one "
1743+
"site, using out-of-process iframes when needed. NOTE: Site isolation is "
1744+
"enabled by default on desktop platforms regardless of how this flag is "
1745+
"set; see chrome://process-internals for whether it is currently enabled. "
1746+
"Setting this flag to 'Enabled' turns on site isolation regardless of the "
1747+
"default. Here, 'Disabled' is a legacy value that actually means "
1748+
"'Default,' in which case site isolation may be already enabled based on "
1749+
"platform, enterprise policy, or field trial. See also "
1750+
"#site-isolation-trial-opt-out for how to disable site isolation for "
1751+
"testing.";
17461752

17471753
const char kSiteIsolationTrialOptOutName[] = "Site isolation trial opt-out";
17481754
const char kSiteIsolationTrialOptOutDescription[] =
1749-
"Opts out of field trials that enable site isolation modes "
1755+
"Opts out of field trials and defaults that enable site isolation modes "
17501756
"(SitePerProcess, IsolateOrigins, etc). Intended for diagnosing bugs that "
17511757
"may be due to out-of-process iframes. Opt-out has no effect if site "
17521758
"isolation is force-enabled via #enable-site-per-process or enterprise "

0 commit comments

Comments
 (0)