In the newest nightly builds (8/4/02) the forward and back menu commands are command ] or command [. Please put them back to arrows, there are several reasons for doing this. First, all other browsers are set up like that, second Microsoft mice are set up to use those keys for forward and back (and can't be changed). Third, it's easier to use arrow keys then it is to use the bracket keys. Forth, Chimera started with arrows keys, then moved to bracket keys, people hated it, so they moved it back to arrows. But now, for some reason they are back as brackets...sigh.
I agree, the arrow keys are much more accessible, especially on International layouts where the brackets are buried under multiple modifier keys. Why not just have Command-Arrowkeys mirror the functionality of Command-Brackets? Best of both worlds.
Will, the command+arrows combinations are reserved by Apple for text field navigation. Recommend WONTFIX.
Greg, I'm all for following HIG as much as the next guy, but you rarely need to use editfields in a browser while you're always using the forward-back command. Thus, it should be mapped to the simpliest/most obvious key combo possible.
I agree with Greg. Users of web-based email services and similar web apps use textfields *quite* often, and the behaviour of those fields should follow the expected navigation shortcuts. In addition, Cmd- have been standard back/ forward shortcuts in Mac browsers for a looong time. Recommend WONTFIX
Until Chimera is localizable (bug 150081), shortcuts that are impossible or very hard to type on International layouts should be avoided if at all possible. It's an accessibility and usability issue for most non-Americans. Just implement some checking routines: Command-arrow trapped. Is the user in an editfield? If not, go back. If yes, pass it onto the editfield. This is related to bug 152659 in that it's be easier for the user to tell if an editfield has focus or not if proper Aqua focus rings are used. As a side note, it's not like the current text widgets follow Apple's specs anyway, since they're Gecko stuff.
> As a side note, it's not like the current text widgets follow Apple's specs > anyway, since they're Gecko stuff. They follow most of the key shortcuts for text navigation and selection already. It's difficult for us to allow Command-arrow key combos only when you're not in a text field, because Cocoa gets the key shortcut first, and matches it to the menu items (so it never gets to gecko).
What about when focus is in the URL bar? Command-arrow keys should do text navigation there too.
This bug is really making it hard for me to stay on the nightlies as opposed to 0.4.0. Maybe I'm an old fuddy-duddy but my hands are hardwired to use cmd-arrows for forward and back. I have the feeling that this will be true of the general public. As far as mapping the keys go, you are already handling PageUp and PageDown in some way since they don't function while I'm typing inside a textfield. Since obviously a decision has been made to have that functionality work that way, it can easily be applied to cmd-arrows as well. Also I checked Mozilla 1.1 on mac os x 10.1.5, and they handle textfields (and the uRL bar too, good catch) the way that has been proposed in the comments above. Recommend bumping this bug up to Critical. I forsee a lot of people are going to be irritated if they find that their favorite key combination has been remapped.
Dup. *** This bug has been marked as a duplicate of 160556 ***
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.