Re: New windows not always detected

Brian's Mail list account

Coming in late to this one, and like others no longer have the original message. I posted the other day that sometimes the update for nvda screen opens behind other running aps, and I've also noticed that sometimes a Firefox boot up does not register at all unless you mess about with changing the focus. My initial feelings have always been that some access event is being missed as even on fast machines the log contains watchdog activity such as the core is frozen. and to me that means nvda is effectively suspended and cannot monitor things. I stongly suspect that the programs or events are taking all the resources, maybe only for a split second but its enough to cause the problem so even in process things are not registerd.
Cannot prove it and would have no idea how other screenreaders would work around this, but I put it out there as a suggestion.

Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "nasrin khaksar" <nasrinkhaksar3@...>
To: <>
Sent: Saturday, February 25, 2017 5:07 PM
Subject: Re: [nvda] New windows not always detected

whats your solution for solving this?

On 2/25/17, Gene <gsasner@...> wrote:
I just tested using XP and JAWS. On the three programs where I have this or
a similar problem, it didn't occur with JAWS. I tested opening each program
twice. Though I was skeptical that this was an NVDA problem, it now appears
that it is. Perhaps these programs have something in common that causes
NVDA to have this initial focus problem.

----- Original Message -----
From: Gene
Sent: Saturday, February 25, 2017 2:32 AM
Subject: Re: [nvda] New windows not always detected

I saw a message from an XP user saying that he doesn't encounter the problem
in XP. I still use XP and I see the problem in Firefox, Chrome and Tapin

I didn't keep the message so I can't include it in the quoted previous

----- Original Message -----

From: Dejan Ristic
Sent: Saturday, February 25, 2017 2:29 AM
Subject: Re: [nvda] New windows not always detected

I have encountered it, too.

On 2/25/2017 8:51 AM, Felix G. wrote:


I'd like to ask if anyone else has encountered the following:

When launching an application, for example by hitting enter on Mozilla
Firefox on the desktop, NVDA sometimes fails to detect there is a new active
window. It will not automatically say anything, and pressing NVDA+t will
still yield "Explorer" as if the desktop still had focus. However, pressing
tab clearly shows that Firefox had focus because it performs the expected
action of jumping, for example, out of the address field and into the search

For an experiment I gave it a full five minutes to see if it just takes an
awful lot of time, but no luck. So, window activation events seem under
certain conditions to be able to pass under NVDA's radar.

It might be worth noting that I noticed this not long after a reboot and
the dust might not have fully settled in terms of background tasks starting
and stopping.

Kind regards,



we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages

Join to automatically receive all group messages.