371564 - Disabled keyboard until focus set with mouse, on Alt-Tab to Error Console (or Browser or MailNews)

Status: VERIFIED FIXED

(Core :: DOM: Events, defect)

Description

[Serge Gautherie (:sgautherie)]

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.2pre) Gecko/20070224 SeaMonkey/1.1.1] (nightly) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070220 SeaMonkey/1.5a] (2007-02-20-08-trunk) (W2Ksp4)

No bug.

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070221 SeaMonkey/1.5a] (2007-02-21-09-trunk) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/2007022404 Minefield/3.0a3pre] (nightly) (W2Ksp4)
[Mozilla Thunderbird, version 3 alpha 1 (20070224)] (nightly) (W2Ksp4)

Bug.

I felt like Browser or MailNews windows were loosing focus (whan using Alt-Tab !?) since a few builds.

Steps to reproduce:
1. Start FF/SM/TB with -jsconsole parameter.
2. Press Alt-Tab to go from main window to Error Console.
2r. Alt+"?" or Ctrl+"?" shortcuts do not respond. Only Alt-Space works.

3. Set focus to the input field with the mouse.
3r. All shortcuts work again.

Workaround:
With the Browser and MailNews windows (where/when a focus exists) at least, it seems doing 2 Alt-Tab to go then come back restores the focus...

(I wonder if bug 371045 may be related ??)

My (wild) guess would be bug 261074 could be the cause !?

Comment 1

[Oliver Yeoh]

Yup. Bug 261074 caused this regression.
Patch coming up.

Comment 2

[Oliver Yeoh]

Attachment: Patch

Comment 3

[Ere Maijala (slow)]

Comment on attachment 256354 [details] [diff] [review]
Patch

I didn't even notice, but good.
r=emaijala

Comment 4

[Ere Maijala (slow)]

Fix checked in to trunk.

Comment 5

[Serge Gautherie (:sgautherie)]

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070228 SeaMonkey/1.5a] (nightly) (W2Ksp4)

V.Fixed.

Comment 6

[Serge Gautherie (:sgautherie)]

For the record,
the part that could look like random in reproducing this bug was probably bug 372177.

Comment 7

[Robert Roessler]

Ummm, I don't know why this is reported as being "verified" fixed... I have been grabbing new trunk builds every day or two, and this ugly usability issue has NOT gotten any better!

I am writing this on SM trunk 2007031010, Win XP SP2.

Comment 8

[Serge Gautherie (:sgautherie)]

Are you not rather experiencing bug 372177 ?

Comment 9

[Robert Roessler]

(In reply to comment #8)
> Are you not rather experiencing bug 372177 ?

Maybe, maybe not... there do seem to be multiple bugs filed that are each somewhat narrowly framed.  Hopefully when all are fixed, SM trunks will go back to being as cool as they were. :)

BTW, I am surprised that 372177 didn't make it into today's trunk build(s) - given the time that the "Checked in to trunk." comment was posted, it should have... and it is possible then that we wouldn't be having *this* discussion.

Comment 10

[Serge Gautherie (:sgautherie)]

(In reply to comment #9)
> Maybe, maybe not... there do seem to be multiple bugs filed that are each
> somewhat narrowly framed.

AFAIK, 3 (main) reports: 2 bugs, with different steps.

> BTW, I am surprised that 372177 didn't make it into today's trunk build(s) -
> given the time that the "Checked in to trunk." comment was posted, it should

Hardly, commit and comment happened 1 hour after the build of the 10h.

> have... and it is possible then that we wouldn't be having *this* discussion.

(Maybe, or you could try to look closer ?)

Comment 11

[Robert Roessler]

(In reply to comment #10)
> (In reply to comment #9)
> > BTW, I am surprised that 372177 didn't make it into today's trunk build(s) -
> > given the time that the "Checked in to trunk." comment was posted, it should
> 
> Hardly, commit and comment happened 1 hour after the build of the 10h.

Right, which is why I referred to "today's" trunk builds - it now being late on the 11th where I am... and the mentioned comment was at "2007-03-10 11:08:45 PST".

I did not say I was *running* today's trunk build, just that the fix for 372177 did not seem to be in it.  This is based on the daily report from jasonb in the "SeaMonkey Builds" forum on mozillazine.

> > have... and it is possible then that we wouldn't be having *this* discussion.
> 
> (Maybe, or you could try to look closer ?)

Or not.

Comment 12

[Serge Gautherie (:sgautherie)]

(In reply to comment #11)

I don't know what/who happen on MozillaZine.
Maybe you should not start complaining (here) without having verified anything by yourself:
the fixes *are* in the SM 11th nightly.

Care not to make me/others loose their time ? Thanks.