129173 - Up/down arrows should jump cursor to start/end of line in URL Bar with autocomplete disabled

Status: RESOLVED WORKSFORME

(SeaMonkey :: Location Bar, defect)

Description

[Stanton McCandlish]

When you hit up-arrow in the URL text entry box, cursor should jump to start-of-line, and should jump to 
end-of-line when you hit down-arrow, but this doesn't work.  Instead, some doohickey pops up, below the 
URL entry box.

Maybe this is OK in operating systems in which up and down don't normally have start/end-of-line behavior, 
but in MacOS, these keys *ALWAYS* do this, in the operating system and in any application written in 
conformance with the Apple User Interface specs.  The functions currently assigned to these keys in Mac 
Mozilla should be moved to command-arrow or option-arrow variants instead.

Comment 1

[Stanton McCandlish]

See also bug #129172.

Comment 2

[Greg K.]

Stanton, can you provide the URL of the relevant section in the Apple HIGs?

Comment 3

[Greg K.]

I'll confirm this using Mac/2002091908/9.2.2, with the following caveats.

Up & down arrows are reserved for autocomplete navigation when autocomplete is enabled. In 
this case, the real standard command+left/right serve the purpose.

With autocomplete totally disabled, however, there's no reason the up & down arrows can't fulfill 
this function.

Thus, revising summary.

(Note that the up & down arrows do work as expected in all regular one-line text input fields.)

Comment 4

[timeless]

*** Bug 129172 has been marked as a duplicate of this bug. ***

Comment 5

[Simon Paquet [:sipaq]]

This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".

Comment 6

[Mike Beltzner [:beltzner, not reading bugmail]]

Josh - is this an easy fix for 1.9 for cases where there are no autocomplete results? That's what Safari does ...

Comment 7

[Josh Aas]

I don't know how easy this fix is. It would take me a bit to investigate.

Comment 8

[Stefan [:stefanh]]

This works for me on 2.0.x and trunk (10.6.7 intel), provided that I also turn off the search functionality, of course.