167385 - Loss of focus with new tabs, Mail launch and re-connections

Status: RESOLVED EXPIRED

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Garry Heaton]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826

Mozilla 1.1 (and its predecessors) constantly loses focus when:
1. A new tab is launched with Ctrl+T
2. Mail is launched
3. Re-connecting after a disconnection with Mozilla still running

Reproducible: Always

Steps to Reproduce:
1. Launch Mail in Mozilla 1.1/Linux
2. Launch a new tab in Mozilla 1.1/Linux
3. Keep Mozilla 1.1/Linux running and re-establish PPP connection
Actual Results:  
1. No focus. Have to click mouse in Window before I can use the keyboard
2. Tab is launched but focus disappears. Have to click window before keyboard
can be accessed
3. Mozilla 1.1/Linux won't even access web pages and Mail often refuses to
connect. Requires re-booting Mozilla.

Expected Results:  
1. Mail should be accessible without clicking the window first
2. Tabs should launch allow immediate Ctrl+Shift+L launch without having to
click  window first
3. Should be able to retain connection parameters instead of requiring re-boot
following a disconnection.

The re-connection problems are the most serious but, in general, Mozilla
1.1/Linux doesn't seem to have a clue about retaining focus half of the time. I
use it within KDE if that makes any difference.

I routinely launch Mozilla via the shell with:

$ /usr/local/mozilla/1.1/mozilla &

... so this should prevent any other processes interfering, I would have thought.

Comment 1

[Bob Kanefsky]

I guess this would be either Event Handing or maybe HTML Form Controls.

Reporter:  Did you mean that any one of 1, 2, or 3 would cause focus to be lost,
or that the sequence of 1, 2, and 3 in order will cause it to happen?

I haven't run into most of this myself, but I did run into something like the
tab problem, and I stumbled across this bug when searching for duplicates prior
to reporting a new bug.  Looking a little further, what I ran into is a
duplicate of bug 124750.  This one sounds like something different, though.

Comment 2

[Alexander Opitz]

Reporter can you reproduce this bug with a newer build (1.4 final)?
If not, then please close this bug as worksforme. Thanks.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.