179148 - Focus jumps unexpectedly

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[selmer (gone)]

2002110813 commercial

Several times with this build, focus has jumped to some unexpected place.  It
seems to have something to do with message selection in the thread pane.  Once,
I selected a message and replied to it.  When the reply window went away a
different message was selected in the thread pane without any interaction on my
part.  The second and third times, I selected a message and the focus moved up
to the quick search input field.

Comment 1

[selmer (gone)]

Focus jumping to quicksearch is happening repeatedly.  It seems to be a short
timeout after some messages load in the message pane.

Comment 2

[selmer (gone)]

In case it matters, this has been happening with my view selection in a custom
view that shows only mail from people NOT in my CAB.  I do not yet know if it
happens under other circumstances.

Comment 3

[Frank de Lange]

Here it seems to happen only when the thread pane is set to anything but 'View:
All'. I have not noticed any relationship between the sender of messages and the
focus jump to the quick searchfield. Using linux, CVS updated daily, this has
been happening for several weeks now...

Comment 4

[Peter Simanyi]

I can reproduce the problem where focus jumps
to the quick search field:
(I'm running Redhat 7.2, running Mozilla locally,
version 1.3b.)

Set a View that's not All.
Click on a message to view it.
Click on the Get New Messages icon.
And focus is moved to the quick search field.

The worst part of this is that if I set my
mail fetch interval to 1 minute (which is fine
since my mail server is on my LAN), then my
focus is moved to the quick search field every
60 seconds.

Here's my filter that reproduces this
(regarding selmer's 11-08 comment about NOT):
    Subject doesn't contain [SLE]

Other than this, the mail reader is great and
the threaded view is indispensable. Thanks.

If you people are too busy to fix this,
if someone could append to this bug
a quick pointer
to the code that would handle focus
moving to the quick search field,
I'll try to make a debug build and
analyze this myself in the next 3 weeks.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420