| // Copyright 2020 The Chromium Authors |
| // Use of this source code is governed by a BSD-style license that can be |
| // found in the LICENSE file. |
| |
| #include "components/site_isolation/features.h" |
| |
| #include "build/build_config.h" |
| |
| namespace site_isolation { |
| namespace features { |
| |
| // Controls a mode for dynamically process-isolating sites where the user has |
| // entered a password. This is intended to be used primarily when full site |
| // isolation is turned off. To check whether this mode is enabled, use |
| // SiteIsolationPolicy::IsIsolationForPasswordSitesEnabled() rather than |
| // checking the feature directly, since that decision is influenced by other |
| // factors as well. |
| BASE_FEATURE(kSiteIsolationForPasswordSites, |
| "site-isolation-for-password-sites", |
| // Enabled by default on Android; see https://crbug.com/849815. Note that this |
| // should not affect Android Webview, which does not include this code. |
| #if BUILDFLAG(IS_ANDROID) |
| base::FEATURE_ENABLED_BY_DEFAULT |
| #else |
| base::FEATURE_DISABLED_BY_DEFAULT |
| #endif |
| ); |
| |
| // Controls a mode for dynamically process-isolating sites where the user has |
| // logged in via OAuth. These sites are determined by runtime heuristics. |
| // |
| // This is intended to be used primarily when full site isolation is turned |
| // off. To check whether this mode is enabled, use |
| // SiteIsolationPolicy::IsIsolationForOAuthSitesEnabled() rather than |
| // checking the feature directly, since that decision is influenced by other |
| // factors as well. |
| // |
| // This feature does not affect Android Webview, which does not include this |
| // code. |
| BASE_FEATURE(kSiteIsolationForOAuthSites, |
| "SiteIsolationForOAuthSites", |
| // Enabled by default on Android only; see https://crbug.com/1206770. |
| #if BUILDFLAG(IS_ANDROID) |
| base::FEATURE_ENABLED_BY_DEFAULT |
| #else |
| base::FEATURE_DISABLED_BY_DEFAULT |
| #endif |
| ); |
| |
| #if BUILDFLAG(IS_ANDROID) |
| // kSiteIsolationMemoryThresholdsAndroid is checked before individual site |
| // isolation mode base::Features (such as kSitePerProcess or |
| // kSiteIsolationForPasswordSites), and (if enabled) can restrict those modes |
| // to not apply to low-memory devices below a certain memory threshold. The |
| // threshold for what is considered a "low memory" device can be set (in MB) |
| // via field trial params with the names defined below, with independent params |
| // for strict site isolation (kSitePerProcess) and partial site isolation modes |
| // (kSiteIsolationForPasswordSites, kSiteIsolationForOAuthSites, etc). These |
| // thresholds are compared against base::SysInfo::AmountOfPhysicalMemoryMB(). |
| // On devices below the memory threshold, the site isolation features such as |
| // kSitePerProcess won't be checked at all, and field trials won't activate |
| // either the control or the experiment group. |
| BASE_FEATURE(kSiteIsolationMemoryThresholdsAndroid, |
| "SiteIsolationMemoryThresholds", |
| base::FEATURE_DISABLED_BY_DEFAULT); |
| const char kStrictSiteIsolationMemoryThresholdParamName[] = |
| "strict_site_isolation_threshold_mb"; |
| const char kPartialSiteIsolationMemoryThresholdParamName[] = |
| "partial_site_isolation_threshold_mb"; |
| #endif // BUILDFLAG(IS_ANDROID) |
| |
| // In order to have broader support for JavaScript optimizer exceptions, we'll |
| // apply origin isolation on navigation for URLs that match rules in the |
| // JAVASCRIPT_OPTIMIZER content setting that don't match the default setting. |
| // TODO(crbug.com/413695645): we want this feature to start isolating any origin |
| // that was specified in the rules but there currently isn't a way to determine |
| // this from the host_content_settings_map API, so we'll improve this in the |
| // future. |
| // |
| // On Android, this implicitly starts isolating origins under partial site |
| // isolation. If full site isolation is enabled (examples: through opt-in or an |
| // enterprise policy), then this feature behaves the same as on Desktop. |
| // |
| // On Desktop, this feature starts isolating origins where the custom policy |
| // targets an origin that is not already origin-isolated. |
| BASE_FEATURE(kOriginIsolationForJsOptExceptions, |
| "OriginIsolationForJsOptExceptions", |
| base::FEATURE_ENABLED_BY_DEFAULT); |
| |
| // Desktop-only: kOriginIsolationMemoryThreshold (if enabled) is used to |
| // determine if a device has the necessary resources to participate in origin |
| // isolation (a stronger model than site isolation, but with potentially higher |
| // resource usage). |
| BASE_FEATURE(kOriginIsolationMemoryThreshold, |
| "OriginIsolationMemoryThreshold", |
| base::FEATURE_DISABLED_BY_DEFAULT); |
| const char kOriginIsolationMemoryThresholdParamName[] = |
| "origin_isolation_threshold_mb"; |
| |
| } // namespace features |
| } // namespace site_isolation |
