[Mac] ctrl-n and ctrl-p navigation for autocomplete entries

NEW
Unassigned

Status

()

--
enhancement
13 years ago
4 months ago

People

(Reporter: solushex, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1b2) Gecko/20060817 Firefox/2.0b2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1b2) Gecko/20060817 Firefox/2.0b2

control-n maps to the down arrow key (control-p -> up) for the location/search bar and forms in safari, camino and opera.

firefox has tab (shift-tab) for the url bar but nothing handy for form autocomplete suggestions.

if someone could point out where this is specified in the code i wouldn't mind just fixing this for my own use.

sorry if this should have filed under core and/or location bar and autocomplete.

Reproducible: Always

Updated

13 years ago
Summary: ctrl-n and ctrl-p navigation for autocomplete entries → [Mac] ctrl-n and ctrl-p navigation for autocomplete entries
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 1

11 years ago
i figured out how to do this with the keyconfig extension (thanks to firemacs.xpi):

var controller = Components.classes["@mozilla.org/autocomplete/controller;1"].getService(Components.interfaces.nsIAutoCompleteController);
controller.handleKeyNavigation(KeyEvent.DOM_VK_DOWN);

leaving as new, though it no longer concerns me.

Comment 2

a year ago
[Tracking Requested - why for this release]: This bug could affect Mac users of this release.
status-firefox57: --- → ?
tracking-firefox57: --- → ?

Comment 3

a year ago
The instructions for marking this as affected indicate I should be able to select the "affected" option under Firefox 57 - Status, but I only have the "?" option. Firefox 57 will almost definitely be affected.
Not going to track this for 57. This is a rather old bug, and it is doubtful that it would be a priority for 57.
status-firefox57: ? → ---
tracking-firefox57: ? → ---

Comment 5

a year ago
What would it take to get this prioritized for a soon-ish release?

Comment 6

a year ago
please fix it...

Comment 7

8 months ago
I was wondering if there is a workaround for this issue. If not, what will be the process to get this prioritized?
As far as I can tell, this bug is still valid. Is there anything that can be done to get it moving?
Flags: needinfo?(mozillamarcia.knous)
(In reply to David Teller [:Yoric] (please use "needinfo") from comment #8)
> As far as I can tell, this bug is still valid. Is there anything that can be
> done to get it moving?

Hello David - Probably up to the Engineering team to review and decide.
Flags: needinfo?(mozillamarcia.knous)
You need to log in before you can comment on or make changes to this bug.