Le 07/10/2025 à 02:18, Gregory Nowak a écrit :
> 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.

    Well, I never intended to prize a browser against another. Palemoon
and Firefox are different by definition. I'm pretty sure Firefox is more
on the cutting edge, but it has a trend to introduce user-unfriendly or
ad-friendly features and I understood that this has been the very
motivation for the development of several alternative free browsers,
including Palemoon. As I already wrote, PM is my default browser but it
sometimes fails to properly display a page (or maybe some freakish JS),
in which case I use FF.

    speech-dispatcher wasn't hanging. It was consuming 100% cpu time on
one core, which caused an audible increase of the fan speed, though no
speech.

     Thank to you, I now know for sure that PM isn't for the blind
people, which is unfriendly, but maybe beyond the capabilities of the
development team. Therefore I cannot put a blame on them for that. How
could I blame people delivering for free, anyway?

--     Didier