cmd+left/right to navigate in textfields goes back/fwd instead



Camino Graveyard
Toolbars & Menus
16 years ago
16 years ago


(Reporter: sairuh (rarely reading bugmail), Assigned: Simon Fraser)







16 years ago
found using the 2002.07.12.05 build. unlike in mozilla (on OS X even), the
textfield shortcuts to go to the beginning of a line (command+left) and end of
line (command+right) in chimera go back a page and forward a page. somehow the
page navigation shortcut is overruling the text area shortcuts.

on the other hand, in chimera option+left/right (in text areas) still works by
jumping btwn words. (which is the same as mozilla on OS X.)

suggestion: control+left/right doesn't appear to do anything in either the
textfields or page content in either chimera or mozilla. how about using
control+left/right in chimera? unless it might cause a conflict elsewhere...


16 years ago
Keywords: access

Comment 1

16 years ago
This could be a good argument against using Command+arrows as page navigation.

Comment 2

16 years ago
Technically, cmd-left arrow and cmd-right arrow are reserved by the system to be
used for changing scripts, so we should be using them neither for forward/back
nor as text field shortcuts.

Is there some way we could, say, map back and forward to cmd-[ and cmd-], but
also have left and right arrow work unless they need to be overridden by the
system? We would then also have to make different localized shortcuts for
forward and back, and the people who have non-US keyboards will complain about
having to use a three key shortcut until we get Chimera localized.


Comment 3

16 years ago
Oh, and all cocoa apps are supposed to have option-arrow go forward/back one
word and control-arrow go to the start/end of a line. If there is anywhere in
Chimera where this doesn't work, then that is one of those places where we
aren't using a real cocoa text box and things like services and spell checking
aren't working either. cmd-arrow behaves the same as control-arrow if you are
NOT on an international system, but Chimera shouldn't have to worry about
managing this if we weren't using a reserved shortcut.

Comment 4

16 years ago
The new Jaguar HIG state the commmand-left and command-right should got to
beginning and end of line. The shift modifier changes this move to a select.

So we need to fix both the Back/Forward shortcuts, and the Next/Previous tab

Comment 5

16 years ago
Yes, they are now supposed to move the cursor out by the second degree semanic
unit, and they are still reserved for changing the direction on non-Roman
systems, and every combination of the option, command and shift keys and the
arrow keys is now reserved (pg. 170), so I agree we are going to have to
completely ditch this shortcut now.

"Command–Right Arrow: To the next semantic unit, typically the end of the
current line, then the end of the next line

Command–Left Arrow: To the previous semantic unit, typically the beginning of
the current line, then the previous unit

... ... ...

Note: For non-Roman script systems, Command–Left Arrow and Command–Right Arrow
are reserved for changing the direction of keyboard input."

Comment 6

16 years ago
This is fixed in Chimera 20020730; the commands are now mapped to cmd-[ and ].

Comment 7

16 years ago
I fixed this
Assignee: saari → sfraser

Comment 8

16 years ago
I fixed this by changing the Forward/Back shortcuts from Command-arrows, to
Command-]/Command-[, and the Next/Previous tab shortcuts to Command-}/Command-{
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 9

16 years ago
vrfy'd fixed with 2002.07.31.05 nb.


a. cmd+[ and cmd+] now go back and fwd in session history. they work whether
focus is in a text field or the regular web content.

b. cmd+{ and cmd+} now go back and fwd through multiple tabbed browsers. they
work whether focus is in a text field or the regular web content.

c. cmd+left arrow and cmd+right arrow now only work in text fields (no effect in
regular content), and jump to the beginning and end of a line. cmd+down and
cmd+up go to the beginning and end of the entire text area.

d. cmd+shift+left arrow and cmd+shift+right arrow now only work in text fields
(no effect in regular content), and select from the cursor to the beginning and
end of a line. cmd+shift+down and cmd+shift+up select from the cursor to the
beginning and end of the entire text area.

e. opt+left arrow and opt+right arrow continue to work (text fields only) to
jump backwards and forwards a word at a time.

i found some weird behavior with opt+shift+arrow keys, but will file that

Comment 10

16 years ago
actually, bugs already exist (in the mozilla browser) for word-detection issues
when encountering punctuation: bug 108125 and bug 127321 (bug 98546 is a more
general bug for word-detection).
You need to log in before you can comment on or make changes to this bug.