Closed Bug 682514 Opened 13 years ago Closed 6 years ago

Focus the search box in the add-ons manager

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: buchner.johannes, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #570760 +++

On opening the add-ons manager, search should be focussed so that the user can type away.

This behaviour is similar to 
 * opening a new tab -> url is focused, 
 * GNOME Shell: Expose -> search windows box receives all keystrokes

At the moment, as far as I see (Firefox 6), nothing special is focused. The tab navigation would be the same if starting from the searchbox.
No longer depends on: 570760
In https://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/content/extensions.xul

there is 

textbox id="header-search"

which should receive something like selectedIndex="0" (see view-port) or tabindex="0"?
(In reply to Johannes Buchner from comment #0)
> On opening the add-ons manager, search should be focussed so that the user
> can type away.

You're assuming the user is most likely going to search when opening the add-ons manager.
Why?
(In reply to Dão Gottwald [:dao] from comment #2)
> (In reply to Johannes Buchner from comment #0)
> > On opening the add-ons manager, search should be focussed so that the user
> > can type away.
> 
> You're assuming the user is most likely going to search when opening the
> add-ons manager.
> Why?

I suggest an alternative question, of what?

If there should be a focus (and bug 580537 comment 0 suggests there should be), then *what* should the focus be, if not search?
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE

To be consistent with the Options/Preferences page, this bug should be fixed.

You need to log in before you can comment on or make changes to this bug.