On Mon, Oct 06, 2025 at 11:01:07AM +0200, Didier Kryn wrote:
> Le 06/10/2025 à 00:55, Gregory Nowak a écrit :
> > On Sun, Oct 05, 2025 at 12:26:44PM +0200, Didier Kryn wrote:
> > >     Thanks for the explanation. Too bad that speech-dispatcher is  buggy!
> > Not as buggy as you seem to think.
> >
>     Therefore it must be Firefox that doesn't manage it correctly. Because
> it happened to me quite often with Firefox and only with Firefox. Either
> Palemoon doesn't take care of visually impaired, or it does handle
> speech-dispatcher correctly.

As far as your first point, I'm not sure what interaction you were
experiencing with speech-dispatcher and firefox. If you didn't have
orca running as a sighted user, orca wouldn't be interacting with
firefox, and sending information for speech-dispatcher to speak. If
firefox does something to use speech-dispatcher directly, I'm not
aware of it. It's possible you had orca running without being aware of
it, and orca was sending data to speak to speech-dispatcher. If
speech-dispatcher couldn't output to the audio device, it possibly
could cause processes feeding it data to hang, until it gave up
speaking a chunk of text, and tried speaking another chunk of text. I
don't know if this is actually what was happening or not. If this were
the case, it would happen with every application, not just firefox.

As far as palemoon goes, it isn't accessible under GNU/Linux and
windows. This seems to be by design:

<https://forum.palemoon.org/viewtopic.php?t=25945>

If palemoon works for you better than firefox, then that's great.

Greg


--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc

--
Free domains: http://www.eu.org/ or mail dns-manager@???