Incoming text is periodically not read by screen readers #14834

@codeofdusk commented on GitHub (Aug 10, 2021):

Nope, this looks like a new bug (I asked him to file here).

@codeofdusk commented on GitHub (Aug 10, 2021): Nope, this looks like a new bug (I asked him to file here).

claunia commented

@carlos-zamora commented on GitHub (Aug 10, 2021):

Curious, does this repro in conhost?

@carlos-zamora commented on GitHub (Aug 10, 2021): Curious, does this repro in conhost?

claunia commented

@Neurrone commented on GitHub (Aug 10, 2021):

I believe not from memory but let me test this and I'll double confirm by the end of the week.

@Neurrone commented on GitHub (Aug 10, 2021): I believe not from memory but let me test this and I'll double confirm by the end of the week.

claunia commented

@Neurrone commented on GitHub (Aug 11, 2021):

Confirmed that its only affecting terminal, and I was able to reproduce it 100% of the time.

Set up an instance of postgres (I did it via docker on my development machine)
Connect to Postgres:

docker run -it --rm postgres:13.3 psql -h db -U postgres
Password for user postgres:                                                                                                          
psql (13.3 (Debian 13.3-1.pgdg100+1), server 12.6 (Debian 12.6-1.pgdg100+1))                                                         
Type "help" for help.                                                                                                                
                                                                                                                                     
postgres=# \l                                                                                                                        
                                  List of databases                                                                                  
     Name     |  Owner   | Encoding |  Collate   |   Ctype    |   Access privileges                                                  
--------------+----------+----------+------------+------------+-----------------------                                               
 applications | postgres | UTF8     | en_US.utf8 | en_US.utf8 |                                                                      
 postgres     | postgres | UTF8     | en_US.utf8 | en_US.utf8 |                                                                      
 template0    | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =c/postgres          +                                               
              |          |          |            |            | postgres=CTc/postgres                                                
 template1    | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =c/postgres          +                                               
              |          |          |            |            | postgres=CTc/postgres                                                
(4 rows)                                                                                                                             
                                                                                                                                     
postgres=# \c applications                                                                                                           
psql (13.3 (Debian 13.3-1.pgdg100+1), server 12.6 (Debian 12.6-1.pgdg100+1))                                                         
You are now connected to database "applications" as user "postgres".

All output just before the command \c applications to connect to the applications database reads fine. All new incoming text after that refuses to read, even if I exit the docker container.

@Neurrone commented on GitHub (Aug 11, 2021): Confirmed that its only affecting terminal, and I was able to reproduce it 100% of the time. 1. Set up an instance of postgres (I did it via docker on my development machine) 2. Connect to Postgres: ``` docker run -it --rm postgres:13.3 psql -h db -U postgres Password for user postgres: psql (13.3 (Debian 13.3-1.pgdg100+1), server 12.6 (Debian 12.6-1.pgdg100+1)) Type "help" for help. postgres=# \l List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges --------------+----------+----------+------------+------------+----------------------- applications | postgres | UTF8 | en_US.utf8 | en_US.utf8 | postgres | postgres | UTF8 | en_US.utf8 | en_US.utf8 | template0 | postgres | UTF8 | en_US.utf8 | en_US.utf8 | =c/postgres + | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | en_US.utf8 | en_US.utf8 | =c/postgres + | | | | | postgres=CTc/postgres (4 rows) postgres=# \c applications psql (13.3 (Debian 13.3-1.pgdg100+1), server 12.6 (Debian 12.6-1.pgdg100+1)) You are now connected to database "applications" as user "postgres". ``` All output just before the command `\c applications` to connect to the applications database reads fine. All new incoming text after that refuses to read, even if I exit the docker container.

claunia commented

@Neurrone commented on GitHub (Oct 8, 2021):

Any news on this?

This is something that I run into every day, and can reproduce easily.

@Neurrone commented on GitHub (Oct 8, 2021): Any news on this? This is something that I run into every day, and can reproduce easily.

claunia commented

@zadjii-msft commented on GitHub (Oct 8, 2021):

Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button?

That way you'll be notified of any updates to this thread.

@zadjii-msft commented on GitHub (Oct 8, 2021): Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button? ![image](https://user-images.githubusercontent.com/18356694/91237459-5cbb0c80-e700-11ea-9347-b9b1ec2813b1.png) That way you'll be notified of any updates to this thread.

claunia commented

@codeofdusk commented on GitHub (Nov 22, 2021):

Received another report of this as nvaccess/nvda#13075, but I personally can't repro. Cc @carlos-zamora.

@codeofdusk commented on GitHub (Nov 22, 2021): Received another report of this as nvaccess/nvda#13075, but I personally can't repro. Cc @carlos-zamora.

claunia commented

@Neurrone commented on GitHub (Jan 20, 2022):

Wondering if there's anything I can do to help with reproduction of this bug? As I am able to reproduce this daily and it is a massive pain when output stops being read.

@Neurrone commented on GitHub (Jan 20, 2022): Wondering if there's anything I can do to help with reproduction of this bug? As I am able to reproduce this daily and it is a massive pain when output stops being read.

claunia commented

@zadjii-msft commented on GitHub (Jan 20, 2022):

If you'd like to take a look at the code yourself and investigate, we'd love a PR ☺️ Otherwise at this point it's just waiting for us to have time to come back to this and actually look into it ourselves. Hopefully sometime in the next 6 mos?

@zadjii-msft commented on GitHub (Jan 20, 2022): If you'd like to take a look at the code yourself and investigate, we'd love a PR ☺️ Otherwise at this point it's just waiting for us to have time to come back to this and actually look into it ourselves. Hopefully sometime in the next 6 mos?

claunia commented

@codeofdusk commented on GitHub (Jan 20, 2022):

I suspect that the impending switch to UIA notifications will help with this. CC @carlos-zamora @DHowett

@codeofdusk commented on GitHub (Jan 20, 2022): I suspect that the impending switch to UIA notifications will help with this. CC @carlos-zamora @DHowett

claunia commented

@zadjii-msft commented on GitHub (Mar 10, 2022):

I'm tossing this to @carlos-zamora if he gets a free moment to confirm that this is actually fixed by #12358.

@zadjii-msft commented on GitHub (Mar 10, 2022): I'm tossing this to @carlos-zamora if he gets a free moment to confirm that this is actually fixed by #12358.

claunia commented

@zadjii-msft commented on GitHub (Mar 17, 2022):

We believe that this should be fixed by #12358 (which should ship in the next hotfix version of the Terminal soon^tm). We have not been able to confirm however.

@zadjii-msft commented on GitHub (Mar 17, 2022): We believe that this should be fixed by #12358 (which should ship in the next hotfix version of the Terminal soon<sup>tm</sup>). We have _not_ been able to confirm however.

claunia commented

@codeofdusk commented on GitHub (Mar 17, 2022):

We believe that this should be fixed by #12358

In theory yes, but in practice no. NVDA doesn't yet leverage UIA notifications (see PR nvaccess/nvda#13261) because I want to think carefully about how that should work, and I haven't yet had the cycles to work further on it.

@codeofdusk commented on GitHub (Mar 17, 2022): > We believe that this should be fixed by #12358 In theory yes, but in practice no. NVDA doesn't yet leverage UIA notifications (see PR nvaccess/nvda#13261) because I want to think carefully about how that should work, and I haven't yet had the cycles to work further on it.

claunia commented

@zadjii-msft commented on GitHub (Mar 18, 2022):

Okay thanks for the clarification. Is there an upstream issue on NVDA that we can close this as a duplicate of? (for housekeeping purposes)

@zadjii-msft commented on GitHub (Mar 18, 2022): Okay thanks for the clarification. Is there an upstream issue on NVDA that we can close this as a duplicate of? (for housekeeping purposes)

claunia commented

@carlos-zamora commented on GitHub (Apr 19, 2022):

/dup https://github.com/nvaccess/nvda/pull/13261

@carlos-zamora commented on GitHub (Apr 19, 2022): /dup https://github.com/nvaccess/nvda/pull/13261

claunia commented

@ghost commented on GitHub (Apr 19, 2022):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Apr 19, 2022): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

claunia commented

@Neurrone commented on GitHub (Apr 20, 2022):

I've seen this bug with Narrator, so I believe this is actually a Terminal issue, not NVDA specific.

@Neurrone commented on GitHub (Apr 20, 2022): I've seen this bug with Narrator, so I believe this is actually a Terminal issue, not NVDA specific.

claunia commented

@DHowett commented on GitHub (Apr 20, 2022):

@Neurrone Have you seen this issue with Narrator and Windows Terminal 1.12.10730 or higher? That is the first version that shipped with #12358, which specifically addresses this issue for Narrator.

@DHowett commented on GitHub (Apr 20, 2022): @Neurrone Have you seen this issue with Narrator and Windows Terminal 1.12.10730 or higher? That is the first version that shipped with #12358, which specifically addresses this issue for Narrator.

claunia commented

@carlos-zamora commented on GitHub (Dec 12, 2022):

@codeofdusk told me there's been a lot of reports for this one and he has a consistent repro. Reopening it and assigning it to the current milestone.

@carlos-zamora commented on GitHub (Dec 12, 2022): @codeofdusk told me there's been a lot of reports for this one and he has a consistent repro. Reopening it and assigning it to the current milestone.

claunia commented

@codeofdusk commented on GitHub (Dec 13, 2022):

I discussed this with @simon818. We're both able to consistently repro this by outputting enough text to fill the screen:

Start wt.
Echo 10,000 "a" characters.
Then, echo hello.

Expected: a textChange event is received, NVDA diffs the screen and says "hello".

Actual: After the screen is filled, textChange (and consequently autoread) stops.

UIA notifications are unaffected (or at least not as severely affected).

@codeofdusk commented on GitHub (Dec 13, 2022): I discussed this with @simon818. We're both able to consistently repro this by outputting enough text to fill the screen: 1. Start `wt`. 2. Echo 10,000 "a" characters. 3. Then, `echo hello`. Expected: a `textChange` event is received, NVDA diffs the screen and says "hello". Actual: After the screen is filled, `textChange` (and consequently autoread) stops. UIA notifications are unaffected (or at least not as severely affected).

claunia commented