Focus changes that NVDA doesn't seem to notice


Felix G.
 

Hi!
I was wondering if anyone else has experienced the following phenomenon. Soon after starting Windows, I launch a program, let's say Chrome, and get no feedback whatsoever about it. In particular, the Chrome window title is not announced, and neither is the address bar. To test what NVDA is seeing, I press NVDA+t, and it says "Explorer." However, maintaining the hypothesis that Chrome indeed has focus, I type a web address and press enter, and indeed the site opens in Chrome and is read properly by NVDA.
So, a new window became active, and keyboard focus was on a specific control within this window, but NVDA did not detect this. The NVDA log shows no irregularities.
Any idea what might be going on and how the effect could be prevented? Is it a known fact that Windows sometimes does not raise such important events? Or might there be a timing issue in which NVDA is temporarily overloaded and thus fails to track them? Would that not generate log entries?
Kind regards,
Felix


Quentin Christensen
 

Which version of Windows are you using?  And from the way you've written, I assume Chrome is just an example - it also happens if you open NotePad or Word or Calculator or anything else?

On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@...> wrote:
Hi!
I was wondering if anyone else has experienced the following phenomenon. Soon after starting Windows, I launch a program, let's say Chrome, and get no feedback whatsoever about it. In particular, the Chrome window title is not announced, and neither is the address bar. To test what NVDA is seeing, I press NVDA+t, and it says "Explorer." However, maintaining the hypothesis that Chrome indeed has focus, I type a web address and press enter, and indeed the site opens in Chrome and is read properly by NVDA.
So, a new window became active, and keyboard focus was on a specific control within this window, but NVDA did not detect this. The NVDA log shows no irregularities.
Any idea what might be going on and how the effect could be prevented? Is it a known fact that Windows sometimes does not raise such important events? Or might there be a timing issue in which NVDA is temporarily overloaded and thus fails to track them? Would that not generate log entries?
Kind regards,
Felix




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Mohammadreza Rashad
 

I have same issue with Firefox. NVDA 17.3 on Windows 10.1703.


On Sep 11, 2017 11:04 AM, "Felix G." <constantlyvariable@...> wrote:
Hi!
I was wondering if anyone else has experienced the following phenomenon. Soon after starting Windows, I launch a program, let's say Chrome, and get no feedback whatsoever about it. In particular, the Chrome window title is not announced, and neither is the address bar. To test what NVDA is seeing, I press NVDA+t, and it says "Explorer." However, maintaining the hypothesis that Chrome indeed has focus, I type a web address and press enter, and indeed the site opens in Chrome and is read properly by NVDA.
So, a new window became active, and keyboard focus was on a specific control within this window, but NVDA did not detect this. The NVDA log shows no irregularities.
Any idea what might be going on and how the effect could be prevented? Is it a known fact that Windows sometimes does not raise such important events? Or might there be a timing issue in which NVDA is temporarily overloaded and thus fails to track them? Would that not generate log entries?
Kind regards,
Felix


Brian's Mail list account <bglists@...>
 

If you mean can you launch a piece of software and nvda seems not to notice, then yes, and it also happens with other screenreaders. If you have auto say all on for example Firefox often on its first opening will not be apparently in focus will not read the page, but anything that affects the display, say hitting alt or in your case going to the address bar, seems to wake it up. I suspect that nvda does not see the page completed signal or its not sent.
Hard to say, but yes it does happen and the speed of the machine seems to be no indication of when it will or will not work..
For example a program called Belarc advisor looks at your computer and then launches the default browser to see the result. It nearly always seems to not have the browser in the foreground when it finishes, even though its just launched it.
Brian

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

----- Original Message -----
From: "Felix G." <constantlyvariable@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, September 11, 2017 7:33 AM
Subject: [nvda] Focus changes that NVDA doesn't seem to notice


Hi!
I was wondering if anyone else has experienced the following phenomenon.
Soon after starting Windows, I launch a program, let's say Chrome, and get
no feedback whatsoever about it. In particular, the Chrome window title is
not announced, and neither is the address bar. To test what NVDA is seeing,
I press NVDA+t, and it says "Explorer." However, maintaining the hypothesis
that Chrome indeed has focus, I type a web address and press enter, and
indeed the site opens in Chrome and is read properly by NVDA.
So, a new window became active, and keyboard focus was on a specific
control within this window, but NVDA did not detect this. The NVDA log
shows no irregularities.
Any idea what might be going on and how the effect could be prevented? Is
it a known fact that Windows sometimes does not raise such important
events? Or might there be a timing issue in which NVDA is temporarily
overloaded and thus fails to track them? Would that not generate log
entries?
Kind regards,
Felix


Brian's Mail list account <bglists@...>
 

For me its nearly always a browser.
Brian

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

----- Original Message -----
From: "Quentin Christensen" <quentin@nvaccess.org>
To: <nvda@nvda.groups.io>
Sent: Monday, September 11, 2017 7:35 AM
Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice


Which version of Windows are you using? And from the way you've written, I
assume Chrome is just an example - it also happens if you open NotePad or
Word or Calculator or anything else?

On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@gmail.com>
wrote:

Hi!
I was wondering if anyone else has experienced the following phenomenon.
Soon after starting Windows, I launch a program, let's say Chrome, and get
no feedback whatsoever about it. In particular, the Chrome window title is
not announced, and neither is the address bar. To test what NVDA is seeing,
I press NVDA+t, and it says "Explorer." However, maintaining the hypothesis
that Chrome indeed has focus, I type a web address and press enter, and
indeed the site opens in Chrome and is read properly by NVDA.
So, a new window became active, and keyboard focus was on a specific
control within this window, but NVDA did not detect this. The NVDA log
shows no irregularities.
Any idea what might be going on and how the effect could be prevented? Is
it a known fact that Windows sometimes does not raise such important
events? Or might there be a timing issue in which NVDA is temporarily
overloaded and thus fails to track them? Would that not generate log
entries?
Kind regards,
Felix



--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


Felix G.
 

Hi!
Yes, Windows 10 Creator's Update, NVDA 2017.3, and browsers are primarily affected by this. With Notepad or Calculator I can't recall ever observing it, but then again I usually launch a browser first thing.
Kind regards,
Felix

Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> schrieb am Mo., 11. Sep. 2017 um 09:41 Uhr:

For me its nearly always a browser.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, September 11, 2017 7:35 AM
Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice


> Which version of Windows are you using?  And from the way you've written,
> I
> assume Chrome is just an example - it also happens if you open NotePad or
> Word or Calculator or anything else?
>
> On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@...>
> wrote:
>
>> Hi!
>> I was wondering if anyone else has experienced the following phenomenon.
>> Soon after starting Windows, I launch a program, let's say Chrome, and
>> get
>> no feedback whatsoever about it. In particular, the Chrome window title
>> is
>> not announced, and neither is the address bar. To test what NVDA is
>> seeing,
>> I press NVDA+t, and it says "Explorer." However, maintaining the
>> hypothesis
>> that Chrome indeed has focus, I type a web address and press enter, and
>> indeed the site opens in Chrome and is read properly by NVDA.
>> So, a new window became active, and keyboard focus was on a specific
>> control within this window, but NVDA did not detect this. The NVDA log
>> shows no irregularities.
>> Any idea what might be going on and how the effect could be prevented? Is
>> it a known fact that Windows sometimes does not raise such important
>> events? Or might there be a timing issue in which NVDA is temporarily
>> overloaded and thus fails to track them? Would that not generate log
>> entries?
>> Kind regards,
>> Felix
>>
>>
>>
>
>
> --
> Quentin Christensen
> Training and Support Manager
>
> Official NVDA Training modules and expert certification now available:
> http://www.nvaccess.org/shop/
>
> www.nvaccess.org
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess
>





Sally Kiebdaj
 

I have also seen this when opening Firefox but not only when the computer starts. For me, it is any time I launch a Firefox after it was closed. It seems to be a matter of lag as the window will read properly if I wait long enough.

Windows 7 sp1, NVDA 17.3 on a fast machine.

Cheers, Sally


On Sep 11, 2017 05:02, "Felix G." <constantlyvariable@...> wrote:
Hi!
Yes, Windows 10 Creator's Update, NVDA 2017.3, and browsers are primarily affected by this. With Notepad or Calculator I can't recall ever observing it, but then again I usually launch a browser first thing.
Kind regards,
Felix

Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> schrieb am Mo., 11. Sep. 2017 um 09:41 Uhr:
For me its nearly always a browser.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, September 11, 2017 7:35 AM
Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice


> Which version of Windows are you using?  And from the way you've written,
> I
> assume Chrome is just an example - it also happens if you open NotePad or
> Word or Calculator or anything else?
>
> On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@...>
> wrote:
>
>> Hi!
>> I was wondering if anyone else has experienced the following phenomenon.
>> Soon after starting Windows, I launch a program, let's say Chrome, and
>> get
>> no feedback whatsoever about it. In particular, the Chrome window title
>> is
>> not announced, and neither is the address bar. To test what NVDA is
>> seeing,
>> I press NVDA+t, and it says "Explorer." However, maintaining the
>> hypothesis
>> that Chrome indeed has focus, I type a web address and press enter, and
>> indeed the site opens in Chrome and is read properly by NVDA.
>> So, a new window became active, and keyboard focus was on a specific
>> control within this window, but NVDA did not detect this. The NVDA log
>> shows no irregularities.
>> Any idea what might be going on and how the effect could be prevented? Is
>> it a known fact that Windows sometimes does not raise such important
>> events? Or might there be a timing issue in which NVDA is temporarily
>> overloaded and thus fails to track them? Would that not generate log
>> entries?
>> Kind regards,
>> Felix
>>
>>
>>
>
>
> --
> Quentin Christensen
> Training and Support Manager
>
> Official NVDA Training modules and expert certification now available:
> http://www.nvaccess.org/shop/
>
> www.nvaccess.org
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess
>





Felix G.
 

You mean, after opening the window, when you wait for, say, five minutes, it will indeed start reading by itself at some point?
Greetings,
Felix


Sally Kiebdaj <fiddle.pup@...> schrieb am Mo., 11. Sep. 2017 um 13:34 Uhr:

I have also seen this when opening Firefox but not only when the computer starts. For me, it is any time I launch a Firefox after it was closed. It seems to be a matter of lag as the window will read properly if I wait long enough.

Windows 7 sp1, NVDA 17.3 on a fast machine.

Cheers, Sally


On Sep 11, 2017 05:02, "Felix G." <constantlyvariable@...> wrote:
Hi!
Yes, Windows 10 Creator's Update, NVDA 2017.3, and browsers are primarily affected by this. With Notepad or Calculator I can't recall ever observing it, but then again I usually launch a browser first thing.
Kind regards,
Felix

Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> schrieb am Mo., 11. Sep. 2017 um 09:41 Uhr:
For me its nearly always a browser.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, September 11, 2017 7:35 AM
Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice


> Which version of Windows are you using?  And from the way you've written,
> I
> assume Chrome is just an example - it also happens if you open NotePad or
> Word or Calculator or anything else?
>
> On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@...>
> wrote:
>
>> Hi!
>> I was wondering if anyone else has experienced the following phenomenon.
>> Soon after starting Windows, I launch a program, let's say Chrome, and
>> get
>> no feedback whatsoever about it. In particular, the Chrome window title
>> is
>> not announced, and neither is the address bar. To test what NVDA is
>> seeing,
>> I press NVDA+t, and it says "Explorer." However, maintaining the
>> hypothesis
>> that Chrome indeed has focus, I type a web address and press enter, and
>> indeed the site opens in Chrome and is read properly by NVDA.
>> So, a new window became active, and keyboard focus was on a specific
>> control within this window, but NVDA did not detect this. The NVDA log
>> shows no irregularities.
>> Any idea what might be going on and how the effect could be prevented? Is
>> it a known fact that Windows sometimes does not raise such important
>> events? Or might there be a timing issue in which NVDA is temporarily
>> overloaded and thus fails to track them? Would that not generate log
>> entries?
>> Kind regards,
>> Felix
>>
>>
>>
>
>
> --
> Quentin Christensen
> Training and Support Manager
>
> Official NVDA Training modules and expert certification now available:
> http://www.nvaccess.org/shop/
>
> www.nvaccess.org
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess
>





John J. Boyer
 

I use a braille display. When I start Firefox NVDA shows the first link on my home page, because that is where Firefox
has placed the cursor. i have always considered this the natural response. If I want to type something in the address
bar I press Alt+d.

On Mon, Sep 11, 2017 at 08:41:44AM +0100, Brian's Mail list account via Groups.Io wrote:
For me its nearly always a browser.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen"
<quentin@nvaccess.org>
To: <nvda@nvda.groups.io>
Sent: Monday, September 11, 2017 7:35 AM
Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice


Which version of Windows are you using? And from the way you've written,
I
assume Chrome is just an example - it also happens if you open NotePad or
Word or Calculator or anything else?

On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@gmail.com>
wrote:

Hi!
I was wondering if anyone else has experienced the following phenomenon.
Soon after starting Windows, I launch a program, let's say Chrome, and
get
no feedback whatsoever about it. In particular, the Chrome window title
is
not announced, and neither is the address bar. To test what NVDA is
seeing,
I press NVDA+t, and it says "Explorer." However, maintaining the
hypothesis
that Chrome indeed has focus, I type a web address and press enter, and
indeed the site opens in Chrome and is read properly by NVDA.
So, a new window became active, and keyboard focus was on a specific
control within this window, but NVDA did not detect this. The NVDA log
shows no irregularities.
Any idea what might be going on and how the effect could be prevented? Is
it a known fact that Windows sometimes does not raise such important
events? Or might there be a timing issue in which NVDA is temporarily
overloaded and thus fails to track them? Would that not generate log
entries?
Kind regards,
Felix



--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


--
John J. Boyer
Email: john.boyer@abilitiessoft.org
website: http://www.abilitiessoft.org
Status: Company dissolved but website and email addresses live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM services
that are available at no cost


Felix G.
 

Hi!
Yes, that's what I would also consider the natural response. For me, unfortunately, it doesn't always see those focus changes in the first place.
I'll do some more testing with different timing constellations, for example, I'll wait until hard drive activity is very low before trying again. Maybe there's a pattern.
Any ideas, anyone, if it's Windows not raising the events, or NVDA failing to process them? Is there a way to find out easily?
Greetings,
Felix

John J. Boyer <john.boyer@...> schrieb am Mo., 11. Sep. 2017 um 16:14 Uhr:

I use a braille display. When I start Firefox NVDA shows the first link on my home page, because that is where Firefox
has placed the cursor. i have always considered this the natural response. If I want to type something in the address
bar I press Alt+d.

On Mon, Sep 11, 2017 at 08:41:44AM +0100, Brian's Mail list account via Groups.Io wrote:
> For me its nearly always a browser.
> Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal email to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message ----- From: "Quentin Christensen"
> <quentin@...>
> To: <nvda@nvda.groups.io>
> Sent: Monday, September 11, 2017 7:35 AM
> Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice
>
>
> >Which version of Windows are you using?  And from the way you've written,
> >I
> >assume Chrome is just an example - it also happens if you open NotePad or
> >Word or Calculator or anything else?
> >
> >On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@...>
> >wrote:
> >
> >>Hi!
> >>I was wondering if anyone else has experienced the following phenomenon.
> >>Soon after starting Windows, I launch a program, let's say Chrome, and
> >>get
> >>no feedback whatsoever about it. In particular, the Chrome window title
> >>is
> >>not announced, and neither is the address bar. To test what NVDA is
> >>seeing,
> >>I press NVDA+t, and it says "Explorer." However, maintaining the
> >>hypothesis
> >>that Chrome indeed has focus, I type a web address and press enter, and
> >>indeed the site opens in Chrome and is read properly by NVDA.
> >>So, a new window became active, and keyboard focus was on a specific
> >>control within this window, but NVDA did not detect this. The NVDA log
> >>shows no irregularities.
> >>Any idea what might be going on and how the effect could be prevented? Is
> >>it a known fact that Windows sometimes does not raise such important
> >>events? Or might there be a timing issue in which NVDA is temporarily
> >>overloaded and thus fails to track them? Would that not generate log
> >>entries?
> >>Kind regards,
> >>Felix
> >>
> >>
> >>
> >
> >
> >--
> >Quentin Christensen
> >Training and Support Manager
> >
> >Official NVDA Training modules and expert certification now available:
> >http://www.nvaccess.org/shop/
> >
> >www.nvaccess.org
> >Facebook: http://www.facebook.com/NVAccess
> >Twitter: @NVAccess
> >
>
>
>
>

--
John J. Boyer
Email: john.boyer@...
website: http://www.abilitiessoft.org
Status: Company dissolved but website and email addresses  live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM services
        that are available at no cost






John J. Boyer
 

I have a new Windows 10 machine with a 1 TB hard drive and 8 GB of RAM. Machine speed may have something to do with it.

On Mon, Sep 11, 2017 at 02:57:20PM +0000, Felix G. wrote:
Hi!
Yes, that's what I would also consider the natural response. For me,
unfortunately, it doesn't always see those focus changes in the first place.
I'll do some more testing with different timing constellations, for
example, I'll wait until hard drive activity is very low before trying
again. Maybe there's a pattern.
Any ideas, anyone, if it's Windows not raising the events, or NVDA failing
to process them? Is there a way to find out easily?
Greetings,
Felix

John J. Boyer <john.boyer@abilitiessoft.org> schrieb am Mo., 11. Sep. 2017
um 16:14 Uhr:

I use a braille display. When I start Firefox NVDA shows the first link on
my home page, because that is where Firefox
has placed the cursor. i have always considered this the natural response.
If I want to type something in the address
bar I press Alt+d.

On Mon, Sep 11, 2017 at 08:41:44AM +0100, Brian's Mail list account via
Groups.Io wrote:
For me its nearly always a browser.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen"
<quentin@nvaccess.org>
To: <nvda@nvda.groups.io>
Sent: Monday, September 11, 2017 7:35 AM
Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice


Which version of Windows are you using? And from the way you've
written,
I
assume Chrome is just an example - it also happens if you open NotePad
or
Word or Calculator or anything else?

On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@gmail.com
wrote:

Hi!
I was wondering if anyone else has experienced the following
phenomenon.
Soon after starting Windows, I launch a program, let's say Chrome, and
get
no feedback whatsoever about it. In particular, the Chrome window title
is
not announced, and neither is the address bar. To test what NVDA is
seeing,
I press NVDA+t, and it says "Explorer." However, maintaining the
hypothesis
that Chrome indeed has focus, I type a web address and press enter, and
indeed the site opens in Chrome and is read properly by NVDA.
So, a new window became active, and keyboard focus was on a specific
control within this window, but NVDA did not detect this. The NVDA log
shows no irregularities.
Any idea what might be going on and how the effect could be prevented?
Is
it a known fact that Windows sometimes does not raise such important
events? Or might there be a timing issue in which NVDA is temporarily
overloaded and thus fails to track them? Would that not generate log
entries?
Kind regards,
Felix



--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


--
John J. Boyer
Email: john.boyer@abilitiessoft.org
website: http://www.abilitiessoft.org
Status: Company dissolved but website and email addresses live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM
services
that are available at no cost





--
John J. Boyer
Email: john.boyer@abilitiessoft.org
website: http://www.abilitiessoft.org
Status: Company dissolved but website and email addresses live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM services
that are available at no cost


Gene
 

I haven't tested this in Windows 7.  I havbe a Windows 7 machine but I seldom use it on line, using it instead as a recording machine with my stereo, TV radio, and other such uses.  I go online with it on occasion but not regularly. 
 
In Windows XP, when I launch firefox or Chrome, it either takes a long time for NVDA to move to the browser wwindow, or I may have to go to the desktop and then alt tab around to get NVDA to be aware of the Window.  Often, if I just tab around, it is unaware of the window. 
 
It sounds as though this, or a similar problem, or at least a problem with similar symptoms, is seen in later versions of Windows.  In most programs, I don't have this problem but it isn't just browsers.  Tapin Radio is another program with similar behavior.
 
Gene

----- Original Message -----
From: Felix G.
Sent: Monday, September 11, 2017 9:57 AM
Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice

Hi!
Yes, that's what I would also consider the natural response. For me, unfortunately, it doesn't always see those focus changes in the first place.
I'll do some more testing with different timing constellations, for example, I'll wait until hard drive activity is very low before trying again. Maybe there's a pattern.
Any ideas, anyone, if it's Windows not raising the events, or NVDA failing to process them? Is there a way to find out easily?
Greetings,
Felix

John J. Boyer <john.boyer@...> schrieb am Mo., 11. Sep. 2017 um 16:14 Uhr:
I use a braille display. When I start Firefox NVDA shows the first link on my home page, because that is where Firefox
has placed the cursor. i have always considered this the natural response. If I want to type something in the address
bar I press Alt+d.

On Mon, Sep 11, 2017 at 08:41:44AM +0100, Brian's Mail list account via Groups.Io wrote:
> For me its nearly always a browser.
> Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal email to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message ----- From: "Quentin Christensen"
> <quentin@...>
> To: <nvda@nvda.groups.io>
> Sent: Monday, September 11, 2017 7:35 AM
> Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice
>
>
> >Which version of Windows are you using?  And from the way you've written,
> >I
> >assume Chrome is just an example - it also happens if you open NotePad or
> >Word or Calculator or anything else?
> >
> >On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@...>
> >wrote:
> >
> >>Hi!
> >>I was wondering if anyone else has experienced the following phenomenon.
> >>Soon after starting Windows, I launch a program, let's say Chrome, and
> >>get
> >>no feedback whatsoever about it. In particular, the Chrome window title
> >>is
> >>not announced, and neither is the address bar. To test what NVDA is
> >>seeing,
> >>I press NVDA+t, and it says "Explorer." However, maintaining the
> >>hypothesis
> >>that Chrome indeed has focus, I type a web address and press enter, and
> >>indeed the site opens in Chrome and is read properly by NVDA.
> >>So, a new window became active, and keyboard focus was on a specific
> >>control within this window, but NVDA did not detect this. The NVDA log
> >>shows no irregularities.
> >>Any idea what might be going on and how the effect could be prevented? Is
> >>it a known fact that Windows sometimes does not raise such important
> >>events? Or might there be a timing issue in which NVDA is temporarily
> >>overloaded and thus fails to track them? Would that not generate log
> >>entries?
> >>Kind regards,
> >>Felix
> >>
> >>
> >>
> >
> >
> >--
> >Quentin Christensen
> >Training and Support Manager
> >
> >Official NVDA Training modules and expert certification now available:
> >http://www.nvaccess.org/shop/
> >
> >www.nvaccess.org
> >Facebook: http://www.facebook.com/NVAccess
> >Twitter: @NVAccess
> >
>
>
>
>

--
John J. Boyer
Email: john.boyer@...
website: http://www.abilitiessoft.org
Status: Company dissolved but website and email addresses  live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM services
        that are available at no cost






 

Sometimes I get this in mozilla software thunderbird, firefox, sometimes on a web page, sometimes if I open bt sync and the program for mozilla whatever it is is running.

Nvda looses focus and I go to desktop and it basically doesn't anounce much bar a few tabs.

I get to system tray hit n hit app key and am able to quit nvda then restart it.

It happens a lot more than I'd like enough that I am annoyed by it not enough for me to downgrade, it did this a lot in aniversary win10, less in creaters but still does it if I don't watch it.

Its happened ever since 16.4 or was it 17.1.

Its been round a while.

The only reason I don't put it out is that it happens hardly enough to be a show stopper but does happen enough that I am carefull.

On 11/09/2017 6:33 p.m., Felix G. wrote:
Hi!
I was wondering if anyone else has experienced the following phenomenon.
Soon after starting Windows, I launch a program, let's say Chrome, and get
no feedback whatsoever about it. In particular, the Chrome window title is
not announced, and neither is the address bar. To test what NVDA is seeing,
I press NVDA+t, and it says "Explorer." However, maintaining the hypothesis
that Chrome indeed has focus, I type a web address and press enter, and
indeed the site opens in Chrome and is read properly by NVDA.
So, a new window became active, and keyboard focus was on a specific
control within this window, but NVDA did not detect this. The NVDA log
shows no irregularities.
Any idea what might be going on and how the effect could be prevented? Is
it a known fact that Windows sometimes does not raise such important
events? Or might there be a timing issue in which NVDA is temporarily
overloaded and thus fails to track them? Would that not generate log
entries?
Kind regards,
Felix


Felix G.
 

Hello!
It just happened for me in Win 7 when starting Chrome. I got no feedback so I pressed NVDA+F1 to log information about the current navigator object, which should be tracking focus. Here is what it says:
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (09:43:25.430):
Developer info for navigator object:
name: None
role: ROLE_UNKNOWN
states: 
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.IAccessible.IAccessible object at 0x051DA850>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: None
value: None
appModule: <'appModuleHandler' (appName u'chrome', process ID 4728) at address 51da550>
appModule.productName: u'Google Chrome'
appModule.productVersion: u'61.0.3163.79'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 328820
windowClassName: u'Chrome_WidgetWin_1'
windowControlID: 0
windowStyle: 382664704
windowThreadID: 4580
windowText: u'Neuer Tab - Google Chrome'
displayText: exception: 'NoneType' object is not iterable
IAccessibleObject: <POINTER(IAccessible) ptr=0x80f2f88 at 51ba260>
IAccessibleChildID: -1
IAccessible event parameters: windowHandle=328820, objectID=-4, childID=-1
IAccessible accName: exception: (-2147024809, 'Falscher Parameter.', (None, None, None, 0, None))
IAccessible accRole: exception: (-2147024809, 'Falscher Parameter.', (None, None, None, 0, None))
IAccessible accState: exception: (-2147024809, 'Falscher Parameter.', (None, None, None, 0, None))
IAccessible accDescription: exception: (-2147024809, 'Falscher Parameter.', (None, None, None, 0, None))
IAccessible accValue: exception: (-2147024809, 'Falscher Parameter.', (None, None, None, 0, None))


So the navigator object, although configured to track focus, is on something which isn't even focusable.
Hope this helps in investigating.
Kind regards,
Felix


Shaun Everiss <sm.everiss@...> schrieb am Di., 12. Sep. 2017 um 03:11 Uhr:

Sometimes I get this in mozilla software thunderbird, firefox, sometimes
on a web page, sometimes if I open bt sync and the program for mozilla
whatever it is is running.

Nvda looses focus and I go to desktop and it basically doesn't anounce
much bar a few tabs.

I get to system tray hit n hit app key and am able to quit nvda then
restart it.

It happens a lot more than I'd like enough that I am annoyed by it not
enough for me to downgrade, it did this a lot in aniversary win10, less
in creaters but still does it if I don't watch it.

Its happened ever since 16.4 or was it 17.1.

Its been round a while.

The only reason I don't put it out is that it happens hardly enough to
be a show stopper but does happen enough that I am carefull.




On 11/09/2017 6:33 p.m., Felix G. wrote:
> Hi!
> I was wondering if anyone else has experienced the following phenomenon.
> Soon after starting Windows, I launch a program, let's say Chrome, and get
> no feedback whatsoever about it. In particular, the Chrome window title is
> not announced, and neither is the address bar. To test what NVDA is seeing,
> I press NVDA+t, and it says "Explorer." However, maintaining the hypothesis
> that Chrome indeed has focus, I type a web address and press enter, and
> indeed the site opens in Chrome and is read properly by NVDA.
> So, a new window became active, and keyboard focus was on a specific
> control within this window, but NVDA did not detect this. The NVDA log
> shows no irregularities.
> Any idea what might be going on and how the effect could be prevented? Is
> it a known fact that Windows sometimes does not raise such important
> events? Or might there be a timing issue in which NVDA is temporarily
> overloaded and thus fails to track them? Would that not generate log
> entries?
> Kind regards,
> Felix
>