Focus problems after alt-tab window switching



16 years ago
14 years ago


(Reporter: pladd, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925

Focus on the edit field is incorrectly restored when switching from the composer
window and back using alt-tab.  The arrow keys work, but text can't be typed
until  focus is activated by clicking with the mouse.

Reproducible: Always

Steps to Reproduce:
1. Open composer window
2. alt-tab to another window
3. alt-tab back to composer window
4. Attempt to type text

Actual Results:  
The cursor is correctly placed, but no text comes out. Arrow keys do work for

Expected Results:  
Focus should be restored to the state it was in when switched away.

Comment 1

16 years ago
Could this have to do with bug #120148 -- "Tabs don't remember which element
[frame, textfield, etc] was focused when switching tabs"??  A possible dup??

Just recently send an email to QA Contact, from this bug
report and to QA Contact, from bug #120148.

Comment 2

15 years ago
I can (and often do) duplicate this in Thunderbird 0.5 as well.. it's 
maddening.  Probably the same bug as 212529 and 223974.

Comment 3

15 years ago
Worksforme with 20040324 windows build on XP. I can alt tab to another window,
alt tab return to composer and keep typing with no problem.
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME

Comment 4

15 years ago
This bug may be system-dependent... I can reproduce it trivially on one PC 
running the 03/25 nightly Thunderbird (with an nVidia graphics card) but not 
on another (with an ATI card).  On the nVidia system, the bug only happens 
when nVidia's nView, their multi-monitor support, is enabled.  Zook, Patrick, 
are you using nVidia cards, by chance?

Comment 5

15 years ago
Specifically, this problem only seems to occur when "Enable nView task 
switcher" is set in the User Interface options page of nView.  The workaround 
is obvious, of course...

Comment 6

15 years ago
Nope, don't have the nVidia cards.  Something about Intel Card...
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.