[KeyboardLock] Enabling API and system-lock by default

Enabling the feature for Canary/Dev by default.  We are working
through the final signoffs for the feature and want to start getting
stability info and test feedback from dev/canary.

BUG=680809

Change-Id: I93bdc72aac156668ed758572066a2da29d4d684b
Reviewed-on: https://chromium-review.googlesource.com/1058928Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558765}

content/public/common/content_features.cc

@@ -172,7 +172,7 @@ const char kIsolateOriginsFieldTrialParamName[] = "OriginsList";
 // Enables an API which allows websites to capture reserved keys in fullscreen.
 // Defined by w3c here: https://w3c.github.io/keyboard-lock/
 const base::Feature kKeyboardLockAPI{"KeyboardLockAPI",
-                                     base::FEATURE_DISABLED_BY_DEFAULT};
+                                     base::FEATURE_ENABLED_BY_DEFAULT};
 
 const base::Feature kLayeredAPI{"LayeredAPI",
                                 base::FEATURE_DISABLED_BY_DEFAULT};

ui/base/ui_base_features.cc

@@ -44,7 +44,7 @@ const base::Feature kSecondaryUiMd = {"SecondaryUiMd",
 
 // Allows system keyboard event capture when |features::kKeyboardLockApi| is on.
 const base::Feature kSystemKeyboardLock{"SystemKeyboardLock",
-                                        base::FEATURE_DISABLED_BY_DEFAULT};
+                                        base::FEATURE_ENABLED_BY_DEFAULT};
 
 const base::Feature kTouchableAppContextMenu = {
     "EnableTouchableAppContextMenu", base::FEATURE_DISABLED_BY_DEFAULT};