|
|
DescriptionAdd checking queue size when calling handleSpeakingCompleted().
Some speech contents are not removed when is called by async.
In this case, when call to speak() function twice, second data is not removed in queue.
So I add routine in handleSpeakingCompleted() that is start to speak() function immediately when latest queue size is not 0.
It also works fine if called by asynchronous repeatedly.
BUG=405585
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=180813
Patch Set 1 #
Total comments: 1
Patch Set 2 : Add new flag "shouldStartSpeaking" and remove flag "didJustFinishCurrentUtterance" #Messages
Total messages: 22 (0 generated)
PTAL
https://codereview.chromium.org/495603002/diff/1/Source/modules/speech/Speech... File Source/modules/speech/SpeechSynthesis.cpp (right): https://codereview.chromium.org/495603002/diff/1/Source/modules/speech/Speech... Source/modules/speech/SpeechSynthesis.cpp:157: int oldQueueSize = 0; Can we introduce something like a |shouldStartSpeaking| flag and remove |didJustFinishCurrentUtterance| and |oldQueueSize|? bool shouldStartSpeaking = false; if (utterance == currentSpeechUtterance()) { m_utteranceQueue.removeFirst(); shouldStartSpeaking = !!m_utteranceQueue.size(); }
On 2014/08/21 01:01:22, haraken wrote: > https://codereview.chromium.org/495603002/diff/1/Source/modules/speech/Speech... > File Source/modules/speech/SpeechSynthesis.cpp (right): > > https://codereview.chromium.org/495603002/diff/1/Source/modules/speech/Speech... > Source/modules/speech/SpeechSynthesis.cpp:157: int oldQueueSize = 0; > > Can we introduce something like a |shouldStartSpeaking| flag and remove > |didJustFinishCurrentUtterance| and |oldQueueSize|? > > bool shouldStartSpeaking = false; > if (utterance == currentSpeechUtterance()) { > m_utteranceQueue.removeFirst(); > shouldStartSpeaking = !!m_utteranceQueue.size(); > } I agree your opinion. "didJustFinishCurrentUtterance" flag is not needed. Now I upload new patch. could you check it?
LGTM
The CQ bit was checked by djmix.kim@samsung.com
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/djmix.kim@samsung.com/495603002/20001
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_chromium_gn_compile_rel on tryserver.blink (http://build.chromium.org/p/tryserver.blink/builders/android_chromium_gn_comp...) linux_gpu_triggered_tests on tryserver.chromium.gpu (http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu_trigger...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_rel on tryserver.blink (http://build.chromium.org/p/tryserver.blink/builders/android_chromium_gn_comp...)
The CQ bit was checked by djmix.kim@samsung.com
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/djmix.kim@samsung.com/495603002/20001
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_chromium_gn_compile_rel on tryserver.blink (http://build.chromium.org/p/tryserver.blink/builders/android_chromium_gn_comp...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_rel on tryserver.blink (http://build.chromium.org/p/tryserver.blink/builders/android_chromium_gn_comp...)
The CQ bit was checked by djmix.kim@samsung.com
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/djmix.kim@samsung.com/495603002/20001
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_chromium_gn_compile_rel on tryserver.blink (http://build.chromium.org/p/tryserver.blink/builders/android_chromium_gn_comp...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_rel on tryserver.blink (http://build.chromium.org/p/tryserver.blink/builders/android_chromium_gn_comp...)
The CQ bit was checked by djmix.kim@samsung.com
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/djmix.kim@samsung.com/495603002/20001
Message was sent while issue was closed.
Committed patchset #2 (20001) as 180813 |