Index: components/policy/resources/policy_templates.json |
diff --git a/components/policy/resources/policy_templates.json b/components/policy/resources/policy_templates.json |
index df09c8d9ca189dbd110badee0e5fca3f54eb846c..c46f2051c97bb617a30f477f6c9e2f773a0e6bdc 100644 |
--- a/components/policy/resources/policy_templates.json |
+++ b/components/policy/resources/policy_templates.json |
@@ -118,7 +118,7 @@ |
# persistent IDs for all fields (but not for groups!) are needed. These are |
# specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs, |
# because doing so would break the deployed wire format! |
-# For your editing convenience: highest ID currently used: 254 |
+# For your editing convenience: highest ID currently used: 256 |
# |
# Placeholders: |
# The following placeholder strings are automatically substituted: |
@@ -5443,6 +5443,29 @@ |
If this policy is left unset, high contrast mode is disabled initially but can be enabled by the user anytime.''' |
}, |
{ |
+ 'name': 'VirtualKeyboardEnabled', |
+ 'type': 'main', |
+ 'schema': { 'type': 'boolean' }, |
+ 'supported_on': ['chrome_os:34-'], |
+ 'features': { |
+ 'can_be_recommended': True, |
+ 'dynamic_refresh': True, |
+ 'per_profile': True, |
+ }, |
+ 'example_value': True, |
+ 'id': 255, |
+ 'caption': '''Enable on-screen keyboard''', |
+ 'desc': '''Enable the on-screen keyboard accessibility feature. |
+ |
+ If this policy is set to true, the on-screen keyboard will always be enabled. |
+ |
+ If this policy is set to false, the on-screen keyboard will always be disabled. |
+ |
+ If you set this policy, users cannot change or override it. |
+ |
+ If this policy is left unset, the on-screen keyboard is disabled initially but can be enabled by the user anytime.''' |
+ }, |
+ { |
'name': 'ScreenMagnifierType', |
'type': 'int-enum', |
'schema': { |
@@ -5545,6 +5568,28 @@ |
If this policy is left unset, high contrast mode is disabled when the login screen is first shown. Users can enable or disable high contrast mode anytime and its status on the login screen is persisted between users.''', |
}, |
{ |
+ 'name': 'DeviceLoginScreenDefaultVirtualKeyboardEnabled', |
+ 'type': 'main', |
+ 'schema': { 'type': 'boolean' }, |
+ 'supported_on': ['chrome_os:34-'], |
+ 'device_only': True, |
+ 'features': { |
+ 'dynamic_refresh': True, |
+ }, |
+ 'example_value': True, |
+ 'id': 256, |
+ 'caption': '''Set default state of the on-screen keyboard on the login screen''', |
+ 'desc': '''Set the default state of the on-screen keyboard accessibility feature on the login screen. |
+ |
+ If this policy is set to true, the on-screen keyboard will be enabled when the login screen is shown. |
+ |
+ If this policy is set to false, the on-sreen keyboard will be disabled when the login screen is shown. |
+ |
+ If you set this policy, users can temporarily override it by enabling or disabling the on-screen keyboard. However, the user's choice is not persistent and the default is restored whenever the login screen is shown anew or the user remains idle on the login screen for a minute. |
bartfab (slow)
2014/02/11 12:41:37
You forgot to add the pref to recommendation_resto
kevers
2014/02/12 14:54:49
Done.
|
+ |
+ If this policy is left unset, the on-screen keyboard is disabled when the login screen is first shown. Users can enable or disable the on-screen keyboard anytime and its status on the login screen is persisted between users.''', |
+ }, |
+ { |
'name': 'DeviceLoginScreenDefaultScreenMagnifierType', |
'type': 'int-enum', |
'schema': { |