Per https://docs.google.com/document/d/1nepYzsXq3B37e7yFznpewIBn8p7bs_Y_GDKBq2yvHBw/edit?usp=sharing, we need to either implement the Web Bluetooth permission in terms of PermissionContextBase or add the following code in our critical path.
Since PermissionContextBase will store device information on disk, we probably don't want to enable it until the revocation UI is hooked up, which might take longer than M-51.
if (variations::GetVariationParamValue(
“PermissionsKillSwitch”,"Bluetooth") == “blocked”) {
// Log to the developer console.
web_contents->GetMainFrame()->AddMessageToConsole(
content::CONSOLE_MESSAGE_LEVEL_LOG,
base::StringPrintf(
"%s permission has been blocked.",
<name of your permission>));
// The kill switch is enabled for this permission; Block requests.
return CONTENT_SETTING_BLOCK;
}
Comment 1 by jyasskin@chromium.org
, Mar 29 2016