Focus problem on Windows XP SP3 using NVDA next-10380,9ee9b11

[nvaccessAuto]

Reported by PZajda on 2014-02-18 17:37
Hi,

I use NVDA snapshot next-10380,9ee9b11.

I have some problem with focus:

• If I press Alt+Tab, for example only to check what windows are opened, if I give the focus back to the window which already had the focus before, NVDA won't read the new focused object. Instead, if I press Alt+Up it'll say "blank".
  It happens with all application (I tested with Notepad, Notepad++, and some Explorer).
• On Firefox, the problem is different: for the first time I give it the focus, I cannot interact with the window at all. I have to give it the focus back and press tab to allows NVDA to know what is focused.

The problem began after the fix of others focus issues, last Friday if I remind well. Sorry for the delay.
Blocking #3831

[nvaccessAuto]

Comment 1 by briang1 on 2014-02-18 20:57
I cannot get this to occur with the latest snap of next. Can you be a bit more clear. Could I get this with say Firefox and notepad? I just tried this, and although on the first run of Firefox, no focus occured, subsequent openings worked fine. I put this down to the slowness of firefox on first run, and I guess nvda got fed up with hanging about.
However alt tabbing seems fine to me.
I'm using xp pro completely up to date etc. on a 2.66gig pent 4 with 1.5 gig of ram at this time. Firefox 27.

[nvaccessAuto]

Comment 2 by PZajda (in reply to comment 1) on 2014-02-19 12:29
Replying to briang1:

I cannot get this to occur with the latest snap of next. Can you be a bit more clear.

I don't see how I could be more clear, this problem occurs with absolutely all applications, I just gave some examples but if you need some more I just tested with the Skype main Window, VLC, Airfoil, Internet Explorer, and I can test with more apps but the issue will always remind the same.

Could I get this with say Firefox and notepad? I just tried this, and although on the first run of Firefox, no focus occured, subsequent openings worked fine. I put this down to the slowness of firefox on first run, and I guess nvda got fed up with hanging about.

It didn't happen before last week-end.
So I don't think the first run slowness of Firefox which I know is not the problem, I wait the Webvisum alert before trying to read the window so I don't see why I should wait more, and as I said it didn't happened before.

However alt tabbing seems fine to me.

I'm using xp pro completely up to date etc. on a 2.66gig pent 4 with 1.5 gig of ram at this time. Firefox 27.

I use Windows XP Pro XP 3 fully up to date, 4 G of ram, Intel Core 2 Duo CPU 2.60GHz, Firefox 27.0.1.
For all apps: I am in a window, I press alt+Tab and keep alt pressed until the end of manipulations, and press tab until I find the window which was focused before I pressed alt+tab, I release alt, then NVDA doesn't announce the new focused control.
A simpler manipulation : keep alt pressed, press tab then shift+tab and release alt, NVDA doesn't announce the new focus.
I rebooted more than one time since last time I updated NVDA so it isn't a Windows strange behavior due to not have rebooted when required.
For Firefox I have to do it twice and press tab when the window is focused to allow NVDA announce the focus.

[nvaccessAuto]

Comment 3 by jteh on 2014-02-20 10:33
Probably a regression introduced by #3831. My guess (haven't had a chance to test yet) is that we're blocking the switchEnd event. We seem to map that to the desktop window, so we should allow events from that window.

[nvaccessAuto]

Comment 5 by James Teh <jamie@... on 2014-02-22 08:27
In [e3eceac]:

The focus is now restored correctly when releasing alt+tab without actually switching applications in some configurations.

We map switchEnd and some other events to the desktop window because the original window is invalid, so eventHandler.shouldAcceptEvent had to be taught this.
Re #3897.

[nvaccessAuto]

Comment 6 by jteh on 2014-06-24 04:45
Fixed as per comment:5.
Changes:
State: closed