107926 - browser won't accept keyboard input after starting with mailnews+browser

Status: VERIFIED FIXED

(Core :: XUL, defect)

Description

[John Morrison]

From bug 

------- Additional Comments From Per Reedtz Thomsen 2001-10-31 22:11 -------

Just tested on Linux i686 build 2001103108, and it's still broken:

In the first browser window (when you also start with a mailnews window), if 
you
select an item in the personal toolbar, and then try to type in a form field in
the browser pane, or in the location field, you won't be able to.

Reopening.



------- Additional Comments From Per Reedtz Thomsen 2001-10-31 22:21 -------

To be clear, a repro case:

- make sure you are starting both a browser and mailnews window when you 
launch]
- in the browser window (after logging in to your mail accounts) click on an 
item
  in the personal toolbar. Notice that you have to click twice to make the web
  page appear. 
- Now try to type a URL into the location bar, or anything into a form field on 
  the resulting web page. Notice that you are not able to type anywhere in this 
  window.

Side note: All other windows work fine, except the first one. According to
others this only happens when you lauch mozilla with both a browser and a
mailnews window.


-----------------------------------------------

Filing this as a new bug, since the other bug is morphing too much. 

However, with 10/30 linux build, I cannot reproduce given the steps above.

This may be window manager related (key dead and focus stuff has happened 
only in some wm's before) so could you note the window manager and version
and possibly any relevant settings.

Comment 1

[John Morrison]

Oops, I am mistaken. I can reproduce this as described above with 10/30 linux,
gnome+enlightenment (how do I get the wm version number). I have options set so 
that new windows and popups get keyboard focus when they appear, and 'focus 
follows mouse' set.

[Don't know why it worked for me correctly the first few times, and now it's 
busted...].

Comment 2

[John Morrison]

Er, my opening comment was meant to be
  'from bug http://bugzilla.mozilla.org/show_bug.cgi?id=101239'

Comment 3

[Per Reedtz Thomsen]

I am consistently reproing this with KDE 2.1.1 on Linux (RH 7.1).

Comment 4

[saari (gone)]

yeay for OSes with combinatorial event and UI semantics and options

allright, targeting 0.9.7

Comment 5

[Skewer]

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

Comment 6

[Skewer]

Copying nomination keywords from bug 101239.

Comment 7

[Skewer]

Test procedure:

1. Shut down Mozilla. (Reboot, clear all the profiles, or reinstall it for all I
care - this should still happen.)
2. Configure Mozilla to load a browser and mail window on startup.
3. Start Mozilla.
4. Click the Bookmarks button on the personal toolbar. (No response.)
5. Try to use your keyboard for anything. Type into the URL bar. Type in a form.
Use a hotkey. Tab-navigate. Nothing will work - the keyboard is stuck inside the
bookmark menu, as suggested by the appearance of the bookmark window every time
the menu access key "M" is pressed.

The last time I checked (I will do this again when I finish downloading today's
build), there were no JavaScript errors or other paranormal activity when this
happened.

Comment 8

[GavinS]

Is the lack of keyboard input related to bug#107405?

Comment 9

[An-Cheng Huang]

The description in comment #7 by Skewer is exactly what I saw.  I just want
to add two things:
1. The first time I click the "Bookmarks button on the personal toolbar"
   there's no response.  If I click it a second time, it works, but the
   keyboard is dead after the first click as described by Skewer.
2. The "Bookmarks menu on the menubar" works fine and doesn't kill the
   keyboard.

Comment 10

[Skewer]

Saari: It's critical that this bug is fixed before the next major release. Are 
you going to be able to fix it in time or should this bug be reassigned?

Comment 11

[Dimitrios]

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

Comment 12

[Dimitrios]

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

Comment 13

[saari (gone)]

I can no longer reproduce this on win2k with a current trunk build. A fix just
went in for focus that I think fixed a boat load of problems. Please retest with
the current trunk build (sorry, I don't have a linux box right now, but if this
is linux only the bug needs to reflect that).

Comment 14

[saari (gone)]

This seems to be broken only when quick launch is enabled now, which is covered
in  another bug.

Comment 15

[John Morrison]

I can't reproduce this with a current linux mozilla trunk build. (In fact, this
was filed as a Linux-only bug; there is no comment explaining why the Platform
was changed to All)

Comment 16

[saari (gone)]

Fab, marking this bug as fixed then. Don't worry the other bug is a battle
ground of variant reproduceable cases making it a mess. 

Comment 17

[John Morrison]

Ab fab!