WebAPI/BrowserAPI/KeyboardEvent: Difference between revisions

WebAPI/BrowserAPI/KeyboardEvent (view source)

133 bytes added , 12 June 2014

'

Confirmed users

23

edits

@@ Line 349: / Line 349: @@
 # System app should decide how to handle key event when inner iframe did not handle it
+Build time customization detail will be discussed later. Default Policy in System App for 'Power', 'Exit', 'VolumeUp', 'VolumeDown':
+{| class="wikitable"
+|-
+! Key  !! Default Policy
+|-
+| Power || SYSTEM-ONLY
+|-
+| Exit || SYSTEM-ONLY
+|-
+| VolumeUp || APP-CANCELLED
+|-
+| VolumeDown || APP-CANCELLED
+|}
-Here are two possible way to do it (TBD)
+Default Policy for other keys are still TBD.
-# Build time customization - generate json configuration file at build time, and read it at start-up time
-# Run time customization - settings value?
-# Build time + run time
 There is one more thing to do in this part. We only handle 'Power', 'Exit', 'VolumeUp', 'VolumDown' in part 1. But there will be more 'keys' need to be handled. We'll have to create a key mapping and handling table with customization in this part.