SpeechSynthesisUtterance onpause and onresume events do not fire when pausing and resuming speech
Reported by
wahar...@gmail.com,
Jan 6 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.51 Safari/537.36 Steps to reproduce the problem: Please see JSFiddle here for replicating - tested under Windows 7 and 10, including on the latest beta channel version: http://jsfiddle.net/e2q81qLz/14/ What is the expected behavior? When pause and resume functions are called on a SpeechSynthesisUtterance, the onpause and onresume events should fire. What went wrong? Speech is paused or resumed, but the onpause and onresume events do not fire. Did this work before? Yes Tested in Chromium 54.0.2840.0 on Windows 10 and events work as expected Does this work in other browsers? Yes Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Some additional details from my testing (this problem surfaced in our TTS component) is at https://issues.fluidproject.org/browse/FLUID-6103
,
Jan 9 2017
,
Jan 9 2017
Tested the issue on chrome Stable #55.0.2883.87, Canary 57.0.2976.0 in Windows 10.0 & Ubuntu 14.04 and was able to reproduce the issue. Observations: 1)M30 - M40 : Events are not capturing in "SpeechSynthesisUtterance". 2)M40+ : Pause and resume events are not capturing in "SpeechSynthesisUtterance". This is a Non-Regression issue since seeing this from M30 #30.0.1549.0, Making the status to Untriaged so that the issue would get addressed. Note : Not able to reproduce the issue in MAC 10.12. Thank you.
,
Jan 17 2017
hta@, thoughts on this one?
,
Sep 13
Trying to write a detailed test for this revealed that the spec doesn't define when the events fire in the necessary detail: https://github.com/w3c/speech-api/issues/39 https://github.com/w3c/speech-api/issues/40 I also found that Chrome easily gets stuck, reloading the tests over and over will quickly lead to no utterances being made at all. Confirmed that there is a problem, at least.
,
Sep 13
I've sent some tests at https://github.com/web-platform-tests/wpt/pull/12992. Per https://github.com/web-platform-tests/wpt/pull/12992#issuecomment-421079859 this does work in at least Firefox, so a confirmed interop issue. Tested locally on Mac and busted there too.
,
Sep 14
@foolip: I didn't look at your tests but this issue may be related: https://bugs.chromium.org/p/chromium/issues/detail?id=656602 |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by wahar...@gmail.com
, Jan 6 2017