278510 - after adding search toolbar to Bookmarks toolbar, firefox loses keyboard input

Status: RESOLVED INCOMPLETE

(Firefox :: Toolbars and Customization, defect)

Description

[tommi uimonen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050110 Firefox/1.0 (Debian package 1.0+dfsg.1-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050110 Firefox/1.0 (Debian package 1.0+dfsg.1-2)

Adding Search tool to Bookmarks toolbar causes firefox to not respond to
keyboard. This goes away after doing some magic (like pasting from mouse) but
I'm not quite sure about the mechanism, but somehow I have managed to go back to
normal operation.

Reproducible: Always

Steps to Reproduce:
1. Remove search toolbar if already exists, and close the customizing dialog.
2. set Bookmarks toolbar visible (View -> Toolbars -> Bookmarks)
3. add Search tool to Bookmarks toolbar (View -> Toolbars -> Customize.. -> Drag
Search to Bookmarks toolbar
4. Close customizing dialog

Actual Results:  
Can't type to firefox (textboxes, location field, the newly added search tool,
etc), no response from keyboard

Comment 1

[tommi uimonen]

This is not restricted to the Bookmarks toolbar, happens when inserting the
Search tool to anywhere where it is insertable. And not restricted to inserting
the Search tool, removing it also causes this.

Not all keyboard input is lost, arrows and menus work (Alt-F etc), only
alphanumeric characters cannot be typed.

Comment 2

[tommi uimonen]

Well, as it goes.. It is not restricted to Search toolbar either.

So this seems to happen whatever I add or remove to/from the toolbar.

Comment 3

[Thomas Bertels]

Still reproduceable ?

Comment 4

[tommi uimonen]

Not with windows version. Tried with Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12

I'm traveling now, but as soon as I get home, I'll try the linux version.

Comment 5

[Carsten Book [:Tomcat]]

closing as incomplete, no reply. Tommi, feel free to reopen this bug, when you can reproduce this bugreport with Firefox 3.0.1, thanks