283273 - Search bar: cannot drop down list of search engines or access "Add engines..."

Status: VERIFIED FIXED

(Firefox :: Keyboard Navigation, defect, P1)

Description

[Asaf Romano (gone)]

Apparently, there is no way to fire the "Add engines..." command (available from
the engines dropdown menu) using the keyboard.

For the reference, here's what we do for anything else in the search field:
  1. Switching between serach engines is available via Accel+Arrows
  2. "Clear search history" is an entery of the field context menu (AppKey /
Control+Space)

Comment 1

[Aaron Leventhal]

Similar to bug 263853 for URL bar.

The F4 and Alt+down arrow keys should both work to drop down the list. Weird:
the down arrow drops down a different list -- of your recent searches, but you
can't drop that one down with the mouse.

So there are currently two drop downs, one only for the kbd (search history) and
one only for the mouse (engine type), and neither use the normal drop down
commands (F4 and Alt+down).

Comment 2

[Aaron Leventhal]

Attachment: 1) Support Alt+Up/Alt+Down/F4 to open 2) Don't support F4 on Mac OSX, 3) Tooltip enhances accessibility, esp. with a screen reader,

We can fix F4/Alt+Down/Alt+Up for closing later. I know how to do it, but it
must be done in layout/xul/base/src menu code. similar to how it's done for XUL
menulist. That's not as high priority right now because just pressing Alt by
itself, or pressing tab or escape will close the menu. I think Escape is the
most common way in any case.

Comment 3

[Aaron Leventhal]

Checking in browser/base/content/search.xml;
/cvsroot/mozilla/browser/base/content/search.xml,v  <--  search.xml
new revision: 1.25; previous revision: 1.24
done
Checking in browser/locales/en-US/chrome/browser/searchbar.properties;
/cvsroot/mozilla/browser/locales/en-US/chrome/browser/searchbar.properties,v 
<--  searchbar.properties
new revision: 1.3; previous revision: 1.2
done

Comment 4

[Adam Guthrie]

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

Comment 5

[O. Atsushi (Torisugari)]

> // XXX Why did mStringBundle say that formatStringFromName
> is not a method?

mStringBundle.getFormattedString() should work.

Comment 6

[Aaron Leventhal]

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

Comment 7

[:Gavin Sharp [email: [e-mail]]]

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

Comment 8

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1527381