| Sign In/My Account | View Cart |
| Article: |
Cooking with JavaScript & DHTML | |
| Subject: | numbers as option text? | |
| Date: | 2004-01-16 11:02:13 | |
| From: | dannyg1 | |
|
Response to: numbers as option text?
|
||
|
With the onkeydown event, we're dealing with key codes, not character codes. The key codes for the numeric keypad are different from the key codes across the top of the keyboard. But there is an simple relationship between the two sets, and the way to account for it is to insert a small corrector statement in the typeAhead() function after the line that reads: var charCode = evt.keyCode. Here's the new code to add:
|
||
Showing messages 1 through 3 of 3.
delay property of the typeAheadInfo object constructor function.
It's also possible that with so many options, the scripting bogs down with repeated fetches of the options for each keystroke. Perhaps rework the code to perform the retrieval just once (at onload time) and preserve the list in a global variable for faster subsequent retrievals.
delay property of the typeAheadInfo object constructor function.
Thanks,