aboutsummaryrefslogtreecommitdiff
path: root/en/devices/input/keyboard-devices.html
diff options
context:
space:
mode:
Diffstat (limited to 'en/devices/input/keyboard-devices.html')
-rw-r--r--en/devices/input/keyboard-devices.html5
1 files changed, 3 insertions, 2 deletions
diff --git a/en/devices/input/keyboard-devices.html b/en/devices/input/keyboard-devices.html
index 94ff3178..34f3575b 100644
--- a/en/devices/input/keyboard-devices.html
+++ b/en/devices/input/keyboard-devices.html
@@ -229,7 +229,8 @@ type of <code>SPECIAL_FUNCTION</code>) will never be registered as the built-in
regardless of the setting of this property. This is because a special-function
keyboard is by definition not intended to be used for general purpose typing.</p>
<h3 id="example-configurations">Example Configurations</h3>
-<pre><code># This is an example input device configuration file for a built-in
+<pre class="devsite-click-to-copy">
+# This is an example input device configuration file for a built-in
# keyboard that has a DPad.
# The keyboard is internal because it is part of the device.
@@ -245,7 +246,7 @@ keyboard.builtIn = 1
# DPad always means 'up' from the perspective of the user, even when the entire
# device has been rotated.
keyboard.orientationAware = 1
-</code></pre>
+</pre>
<h3 id="compatibility-notes">Compatibility Notes</h3>
<p>Prior to Honeycomb, the keyboard input mapper did not use any configuration properties.
All keyboards were assumed to be physically attached and orientation aware. The default