133771 - Autoreload removes focus

Status: UNCONFIRMED

(Core :: XUL, defect)

Description

[Ben Bucksch (:BenB)]

Reproduction:
1. In the browser, load a page which autoreloads (via meta refresh) every few
seconds (usual on the web are 30-300 seconds).
2. Open Mailnews; try to select several messages at once (shift-click)
3. Open Mailnews HTML Composer; type

Actual result:
Each reload in the browser, even when in the background, removes the focus from
the current window. The browser doesn't seem to get the focus either (at least
its X11 window doesn't).
During step 2: Whenever the page reloads, the marked messages are no blue
anymore, but grey (selected background).
During step 2: Whenever the page reloads, I lose the caret, meaning that
whatever I type goes to /dev/null until I click into the composer again. That's
pretty annoying, when you try to type a longer text, and confusing, if you don't
know the cause.

Expected result:
Background activity has no influence on focus.

Additional comments:
Autoreloads are used for webcams (30-60s) and some frontpages (lycos, cnn, IIRC;
180-300s).

Comment 1

[Samir Gehani]

Focus-related.  Over to bryner for a look/triage.  Punt as needed.  Thanks.

Comment 2

[Yngve Svendsen]

(In reply to comment #0)

This is a major irritant, and it is still present in the current 1.0PR. I
typically run a network status monitor that updates once a minute in one tab,
usually in the background, while I do ordinary bowsing in another tab which is
usually in the foreground. When reading long pages, I like to sit back and use
the space bar to read one screen-full at a time, and this is not possible since
the foreground tab loses focus when the network monitor page reloads.

Comment 3

[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 4

[hauptman]

in the Windows version 3.5.2 is still this problem

Comment 5

[[e-mail]]

I get the feeling that this is fixed on trunk (2.next) by the focus manager?

Comment 6

[Robert Kaiser]

(In reply to comment #4)
> in the Windows version 3.5.2 is still this problem

Firefox having the problem doesn't make it something we need to fix in SeaMonkey.

Comment 7

[Mounir Lamouri (:mounir)]

Could someone provide an url or attach a test case to check this bug?