Closed
Bug 169067
Opened 23 years ago
Closed 22 years ago
up/down arrow keys do not function (start/end) in URL bar
Categories
(Camino Graveyard :: Location Bar & Autocomplete, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adamrice, Assigned: mikepinkerton)
Details
(Keywords: access)
The up and down arrow keys should move the insertion point to the head/tail of
the URL currently showing in the URL bar. Currently, they don't do anything.
I think this is Invalid. Up and down *can* have that function, but here they're
reserved for autocomplete selection.
The real keys the Apple HIG says perform this function are command+left/right,
and they work fine using Chimera/2002091704.
| Assignee | ||
Comment 2•23 years ago
|
||
true, but other cocoa text fields behave this way. i think we can make them
behave "correctly" in the absence of the autocomplete dropdown.
over to brade, polish.
Assignee: pinkerton → brade
URL: (any)
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•23 years ago
|
||
Recent feedback on the list indicates there's a number of people who would like
to see this fixed (personally I think they're right). It's the default behavoir
if you create a new textfield in IB. Pulling out my handy-dandy copy of the AAHIG...
p149
Up Arrow - To the line above, to the nearest character boundary
at the same horizontal location
Down Arrow - To the line below, to the nearest character boundary
at the same horizontal location
(nearest character boundary in the same horizontal direction I think means to
the beginning or end)
Updated•23 years ago
|
Keywords: access
Summary: up/down arrow keys do not function in URL bar → up/down arrow keys do not function (start/end) in URL bar
In panther, using the arrow (up/down, left/right) + command key, works.
This behaviour is consistent in all apps with text fields.
| Assignee | ||
Comment 7•22 years ago
|
||
fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•