Subject: bug#78474: 31.0.50; Wrong char insertion in rxvt

From: Samuel Thibault <[email-masked]>
Date: Wed, 23 Jul 2025 13:55:39 +0200

Eli Zaretskii, le mer. 23 juil. 2025 14:48:32 +0300, a ecrit:
> > From: Andreas Schwab <[email-masked]>
> > Cc: Eli Zaretskii <[email-masked]>,  [email-masked],  Seb Hinderer
> >  <[email-masked]>,  [email-masked],  [email-masked]
> > Date: Wed, 23 Jul 2025 10:06:19 +0200
> > 
> > On Jul 22 2025, Samuel Thibault wrote:
> > 
> > > Andreas Schwab, le mar. 22 juil. 2025 15:48:20 +0200, a ecrit:
> > >> On Jul 21 2025, Samuel Thibault wrote:
> > >> 
> > >> > It is. Cat /dev/vcs, and you have it.
> > >> 
> > >> /dev/vcs contains the rendered contents, so how they were drawn should
> > >> not make any difference.
> > >
> > > The question of this thread piece was not about that, but about screen
> > > readers being able to read the screen without getting announced to
> > > applications in any way.
> > 
> > Since screen readers using /dev/vcs are not affected by this issue they
> > are irrelevant here.
> 
> So what do screen readers which _are_ affected by this issue use?

At-spi, which exposes the graphical interfaces to the screen readers.
Just like the cat /dev/vcs case, applications inside the terminal are
not notified whether a screen reader is reading them or not.

Samuel