|
|
 |
number key navigation
You can capture ntl’s remote control number keys and integrate these with your site’s navigation.
- Include a standard focusable link as well as coding the number key functionality - users are accustomed to using the bounding box for selection and navigation. Also, users have to look away from the screen to use number buttons on their remote control/keyboard.
- Avoid confusing users through having conflicting use of numbers on a single page. For example, don't combine number key navigation with a text input form field on a single page. The numbers can be directly entered into form fields without using a keyboard and this conflicting use of number buttons may confuse the user.
- When using the javascript "onkeyout" handler and "navigator.input.curKey" to intercept remote control/keyboard key presses, you must ensure that the return value of the function call is passed back. If this is not done, then key presses which you are not handling (e.g. back/skip) can be ignored. If the handler is assigned in the HTML body tag, the following JavaScript code should also be included to do this in the body tag:
body onkeyout="return keypressed(),"
When using the javascript "onkeyout" handler and "navigator.input.curKey" to intercept remote control/keyboard key presses, you should also write code to handle it and return "false". when you have finished handling keys in your JavaScript function, you need to return "true" for all the other key presses so that the ntl resident application will handle them as it would normally. An example of this is shown below:
<script>
function keypressed ()
{
if (navigator.input.curKey == ascii code for key I want)
{
//handle key press as required
return false
}
else
{
return true
}
}
}
</script>
Include a bounding box as well as coding the number key functionality - users are accustomed to using the bounding box for both selection and navigation.
Also, users have to look away from the screen to use the number buttons on their remote control/keyboard.
|
|
|
