272661 - [Mac] keyboard navigation fails when form input has focus

Status: RESOLVED WONTFIX

(Firefox :: Keyboard Navigation, defect)

Description

[Bryan Mills]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

When the cursor is inside a textarea or text input of a form, cmd-arrow fails to
work as usual for forward/back.  This is extremely annoying for pages such as
Yahoo! Weather that auto-focus inputs on page load, and serves no useful purpose.

This problem doesn't appear to exist under Windows, so it seems to be mimicry of
bad Safari behavior.

Reproducible: Always
Steps to Reproduce:

Comment 1

[Krishna Sethuraman]

Yup, same here.  I navigate mostly by keyboard, and this definitely affects me too.

Comment 2

[Bryan Mills]

Also a problem for using up and down arrows for scrolling (I can sort of see how
one might want to use those for form auto-fill, but that really should be
something other than plain arrow keys), and for using page-up and page-down for
scrolling (no reason WHATSOEVER why those shouldn't work -- they work under
Safari but not on Windows).  So I load a page and can't use the keyboard to
scroll or fo back until I CLICK somewhere (since there may be arbitrarily many
forms on a page; this problem is confounded by the absolutely horrible tabbing
behavior under OS X even with full keyboard navigation enabled, but that's
another bug and already reported).

Comment 3

[Dean Serenevy]

This also happens in Mozilla.

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041217

Comment 4

[louis bennett]

See also: bug 130380, a similar issue relating to the Location bar.

Comment 5

[Robert Rothenberg]

When there is a form with some input boxes and a select drop-down, I can use the
Tab key to move to the next input box, but if the next object is a select
drop-down, then it focuses on the location bar instead.

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This shouldn't belong to Pinkerton....

Comment 0 is the expected behavior on Mac OS X (cmd-arrow is beginning/end of
line in a text field)....

Comment 7

[Bryan Mills]

Yeah, I suppose it really is expected behavior.  Still, it's really annoying --
maybe it'd be more appropriate to ad focusing to the list of disablable JavaScript.

Comment 8

[Asaf Romano (gone)]

That's the reason Cmd+Arrows aren't the primary keyboard shortcuts for
back/forward (That's, Cmd+[]).

Comment 9

[Craig Hunter]

(In reply to comment #6)
> This shouldn't belong to Pinkerton....
> 
> Comment 0 is the expected behavior on Mac OS X (cmd-arrow is beginning/end of
> line in a text field)....

On Mac OS, in a single line text field, up-arrow goes to the beginning, down-arrow to the end. But not in Firefox. Without cmd-arrow and option-arrow, there would be no keyboard navigation in text fields at all. I really miss up-arrow and down-arrow; they are more convenient than home or end (which also don't work) or any key combination. This is a bug not only in text boxes on a form, but also in the address box.

Comment 10

[Craig Hunter]

(In reply to comment #9)
fyi: My complaint in #9 is handled by bug 231754