chromium: speechSynthesis does not work

[MasseGuillaume]

Steps to reproduce:

nix-env -i speech-dispatcher espeak chromium 
chromium --enable-speech-dispatcher

var msg = new SpeechSynthesisUtterance();
msg.text = "Hello, World!";
msg.lang = "en";
speechSynthesis.speak(msg);

expected: should say hello world obtained: silence

<a href="#" onclick="test()">Test</a>

window.test = function(){
  window.speechSynthesis.onvoiceschanged = function() {
    console.log(window.speechSynthesis.getVoices())
  };
}

expected: should return an non-empty array of SpeechSynthesisVoice obtained: empty array

see: https://jsfiddle.net/wdhLd55r/2/

[stale[bot]]

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.

[pinage404]

I have the same issue with Brave and Firefox :

Steps to reproduce :

1. open browser with speech programs

   nix-shell --packages brave speechd espeak --command "sh -c 'speech-dispatcher --run-single --log-level 5 --timeout 0 & brave --enable-speech-dispatcher https://jsfiddle.net/wdhLd55r/2/'"

2. click on Test

Actual result : No sound

Expected result : Speech

[Elinvention]

@pinage404 while looking for a solution myself, I run into this pr https://github.com/NixOS/nixpkgs/pull/210453 that solved the issue for me on Firefox.

[tomodachi94]

speechd is included in chromium as of https://github.com/NixOS/nixpkgs/pull/133544 (and switched to speechd-minimal in https://github.com/NixOS/nixpkgs/pull/329658). Can anyone reproduce this issue on Chromium?

[djmaze]

Yes, same problem for me with Chromium 130.0.6723.58.