The SpeechSynthesisUtterance onboundary event does not report charIndex correctly on macOS
Reported by
v.v.gutt...@gmail.com,
Feb 27 2018
|
|||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
Steps to reproduce the problem:
1. Make sure, that the utterance queue is clear by calling speechSynthesis.cancel()
1. Create a new SpeechSynthesisUtterance with the voice set to a German ("de-DE") voice.
2. Setup an event handler for the utterances onboundary event that logs the event.charIndex to the console.
3. Add a text to the utterance: "Das Wort E-Mail sorgt für Probleme."
4. Let speechSynthesis speak the utterance.
5. Notice that after "E-Mail" has been spoken, the onboundary event is not fired anymore
What is the expected behavior?
After "E-Mail" has been spoken, onboundary events should be fired for subsequent word-boundaries.
What went wrong?
After the word "E-Mail" has been spoken, no more onboundary events are fired.
Did this work before? N/A
Does this work in other browsers? No
Firefox 58: https://bugzilla.mozilla.org/show_bug.cgi?id=1441503
Safari 11.0.2 has issues as well (not fully tested yet)
Chrome version: 64.0.3282.186 Channel: stable
OS Version: OS X 10.13.2
Flash Version: SpeechSynthesisUtterance onboundary event not correctly reporting charIndex
- No issues under Windows 10 & Firefox 58 or Chrome 64
- There seem to be issues with certain words that have accents (e.g. Sálvàdôr). It shifts the charIndex a few characters forward. Further research required!
- It is not clear if this problem occurs with other languages as well.
,
Feb 27 2018
,
Feb 28 2018
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 64.0.3282.186 and on the latest canary 66.0.3356.0 using Mac 10.13.1 with the below mentioned steps. 1. Launched Chrome 2. Navigated to https://jsbin.com/natayar/edit?js,console We are able to see that all the events are fired when navigated to that URL. Attaching the screen cast of the same for reference. @Reporter: Could you please have a look at the screen cast and let us know if we have missed any thing in the process of reproducing the issue.
,
Feb 28 2018
Thanks for your reply. Please make sure that a German voice is speaking the utterance. Here is an improved test case that allows you to select a German voice: https://jsbin.com/ropiyig/10/edit?js,console,output When you don't see a voice in the list, it is probably because you don't have a German voice installed on your OS. The reported issue only occurs with German voices, thus a German voice must be installed and selected to reproduce the issue. Steps to reproduce using the new test case: 1. Launch Chrome 2. Navigate to https://jsbin.com/ropiyig/10/edit?js,console,output 3. Select a voice in the dropdown 4. Click on the "speak" button (see attached video) Let me know if this helped!
,
Feb 28 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 5 2018
Able to reproduce the issue on Mac 10.13.3 using chrome reported version #64.0.3282.186 and latest canary #67.0.3361.0. Issue is not seen in OS-linux and OS-Win. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Mar 8 2018
Able to reproduce at Chromium 64 at *nix. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by v.v.gutt...@gmail.com
, Feb 27 2018