SpeechSynthesis fails immediately following a call to cancel
Reported by
mich...@truthiness.biz,
Sep 23 2016
|
||
Issue descriptionChrome Version : 53.0.2785.116 (Official Build) m (64-bit) URLs (if applicable) : https://jsfiddle.net/mqjehweh/1/ Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: N/A (Windows only bug, Safari on Windows does not have SpeechSynthesis Firefox: OK Edge: OK What steps will reproduce the problem? (1) Click on the first div. (2) While SpeechSynthesis is speaking, click on the second div. What is the expected result? The current text should stop, and SpeechSynthesis should start to speak the second div. What happens instead? Nothing. window.speechSynthesis.speaking is reporting speaking, but no audio is heard. Please provide any additional information below. Attach a screenshot if possible. Bug is in Windows only, not present in OSX.
,
Jan 27 2017
(Using Chrome 56 64bit on Windows 10 Pro 64bit) It seems to happen with the Windows native voice (unfortunately Chrome only currently provides a single "native" voice that always resolves to Microsoft David if no other voice is installed in the system, e.g. I couldn't get it to use Microsoft Zira). It didn't seem to happen with Google's cloud voices (Google US English Female, Google UK English Female, etc.). I also tried Google's local "US English Female" voice extension: https://chrome.google.com/webstore/detail/us-english-female-text-to/pkidpnnapnfgjhfhkpmjpbckkbaodldb , and the issue didn't seem to occur with it as well (though, unfortunately, once that voice was installed it prevented the Windows native voices to be selected as Chrome seems to limit to only one "native" voice). The workaround I'm currently using is to add a delay of 300ms between the call to 'Cancel()' and a subsequent call to `Speak()`. Unfortunately it is still not 100% reliable even with this additional delay.
,
Sep 11 2017
Hi everyone, I have detected the same problem, in Windows, with de latest stable Chrome, and with any Voice. When the cancel() method executes asynchronously, and if you try to execute the speak() method immediately, then it does not play sound because there is no way to detect that the cancel() method is finished. Please look at this, it seems important. Thank you very much.
,
Sep 12
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 4
The issue is still there I have a similar situation as rotem...@gmail.com |
||
►
Sign in to add a comment |
||
Comment 1 by tkent@chromium.org
, Dec 9 2016