Bugzilla – Bug 3452
Up/down arrow should cycle through characters for last key
Last modified: 2008-12-18 11:38:49 UTC
This is mostly an issue when entering punctuation characters under the 1 key. It's very easy to overshoot the character you're looking for, but using the up and down arrow appears to cycle through the ASCII character set rather than the characters on the key you've just used. Makes entering these characters particularly tough, since they're all on one key. Instead, cycle through the characters on the key corresponding to the character under the cursor. If you zip past the 20th character in the sequence, all you'd need to do is press the down-arrow to get back to it. The same should be done with all the keys, though it's less important when there are only 7 or 9 characters on the key.
The up and down arrow should cycle through the entire character set, starting with the character that's in place. So, for example, if you are hitting "1" to get an "&" and you miss it, going to the next character (*), you should be able to go back to "&" by hitting the down arrow one time. Are you seeing some other behavior?
> The up and down arrow should cycle through the entire character set, starting > with the character that's in place. So, for example, if you are hitting "1" to > get an "&" and you miss it, going to the next character (*), you should be able > to go back to "&" by hitting the down arrow one time. > Are you seeing some other behavior? Yes, I am. That's the behaviour for many, but not all of the characters under the 1 key. Like you say, the arrows cycle through the entire character set - the problem is that the punctuation characters aren't contiguous within that character set.
Jim I remember your comments you posted on the forums regarding this bug. In firmware 54 you should already find that the punctuation characters appear in the same order under the 1 key and for up/down.
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.