Issue metadata
Sign in to add a comment
|
WebSpeech Utterance onboundary callback not firing on ChromeBook V53 (worked on V52)
Reported by
ad...@tdsstudentlogin.com,
Oct 27 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14 Platform: 8530.81.0 Steps to reproduce the problem: 1. Use the provided html test page. 2. Using Chrome 53 and play the text to speech. Notice the tracking is broken What is the expected behavior? What went wrong? In a nutshell, the onboundary callback on the utterance object in WebSpeech is supposed to do a callback on every word and it stopped doing that in V53 on Chromebooks (Chrome for Win V53 works fine). The attached sample code can be used to verify. Did this work before? Yes 52 Does this work in other browsers? N/A Chrome version: 53.0.2785.103 Channel: stable OS Version: 53.0.2785.103 Flash Version: 22.0.0.209-r1
,
Nov 7 2016
,
Nov 16 2016
dmazzoni@, Can you take a look at this? It's affecting standardized test apps that utilize TTS and want to track the audio output. With school testing periods starting very soon this is high priority for them.
,
Nov 16 2016
This is blocking support for us of Chrome version 53+
,
Nov 29 2016
Without this fix, a lot of schools may not be able to use ChromeOS devices. Raising priority to increase awareness.
,
Dec 1 2016
dmazzoni@, do you have time to take a look at this Thursday or Friday?
,
Dec 2 2016
Working on a fix, I'll let you know when ready.
,
Dec 12 2016
I see the same is happening on V55 for Windows... onboundary is not firing.
,
Dec 16 2016
dmazzoni@, can you update the bug with any new info when you get a chance?
,
Dec 21 2016
dmazzoni, have you gotten a chance to look into this yet?
,
Jan 18 2017
@Max - can I get an ETA on this, this is holding up support for the Chrome OS 55.
,
Jan 25 2017
Guys, Client are holding back support issue, can I get some feedback here so I can take it to the client.
,
Feb 1 2017
,
Feb 2 2017
,
Feb 2 2017
,
Feb 2 2017
,
Feb 2 2017
,
Feb 2 2017
Approving merge to M57 Chrome OS.
,
Feb 3 2017
,
Feb 3 2017
CL with the revert has landed in tot (9246.0.0) and M57 https://chromium-review.googlesource.com/?polygerrit=0#/c/435949/
,
Feb 6 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 8 2017
Can we get this merged to 56 so that it will be included in the first refresh for Chrome devices?
,
Feb 8 2017
We're waiting to verify the fix on M57 first
,
Feb 8 2017
the revert has landed on M57 and behaves as expected
,
Feb 10 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 14 2017
Revert was cherry picked into M56
,
Feb 16 2017
,
Feb 17 2017
,
May 15 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jayhlee@google.com
, Nov 7 2016