sensors: Add and use a new #enable-sensor-content-setting flag.
This new flag, enabled by default, that is now used to control the
availability of the content settings UI for the Generic Sensor API.
The UI used to be tied to the #enable-generic-sensor-extra-classes flag,
which is disabled by default and also controls whether non-motion sensors
such as the Ambient Light sensor are available.
We want to make it control only the latter, and leave the UI to this
new flag to make it easier for users to control whether sensors
(Device Motion included) should be enabled or not.
Bug: 796904
Change-Id: I27387b9a935975c732b155c4f146b3ce70d6868f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508401
Reviewed-by: Reilly Grant <[email protected]>
Reviewed-by: Finnur Thorarinsson <[email protected]>
Reviewed-by: Elly Fong-Jones <[email protected]>
Reviewed-by: Dan Beam <[email protected]>
Reviewed-by: Dominick Ng <[email protected]>
Reviewed-by: Balazs Engedy <[email protected]>
Commit-Queue: Raphael Kubo da Costa <[email protected]>
Auto-Submit: Raphael Kubo da Costa <[email protected]>
Cr-Commit-Position: refs/heads/master@{#640259}diff --git a/chrome/browser/about_flags.cc b/chrome/browser/about_flags.cc
index a704ee0..a7c5db8 100644
--- a/chrome/browser/about_flags.cc
+++ b/chrome/browser/about_flags.cc
@@ -2463,6 +2463,10 @@
flag_descriptions::kEnableGenericSensorExtraClassesName,
flag_descriptions::kEnableGenericSensorExtraClassesDescription, kOsAll,
FEATURE_VALUE_TYPE(features::kGenericSensorExtraClasses)},
+ {"enable-sensor-content-setting",
+ flag_descriptions::kEnableSensorContentSettingName,
+ flag_descriptions::kEnableSensorContentSettingDescription, kOsAll,
+ FEATURE_VALUE_TYPE(features::kSensorContentSetting)},
{"expensive-background-timer-throttling",
flag_descriptions::kExpensiveBackgroundTimerThrottlingName,
flag_descriptions::kExpensiveBackgroundTimerThrottlingDescription, kOsAll,
