ichigo.san@ Thanks for the issue.

Tested this issue on Windows 10 and Mac OS 10.12.6 on the reported version 64.0.3282.119, latest Stable 64.0.3282.140 and Canary 66.0.3336.5 by following the below steps.

1. Launched Chrome and navigated to Chrome://flags
2. Set the Autoplay Policy flag to Document user activation is required and relaunched Chrome.
3. Added the Extension Chromevox on Chrome and on clicking on the page, Chromevox is reading the text and no issues are observed.
Attached is the screen cast for reference.

Request you to check and confirm if anything is missed from our end in reproducing the issue. 

Also request you to retry the issue on a new chrome profile and update the thread with the observations.

Thanks..

Deleted: 807538.webm 6.3 MB

	807538.webm 6.3 MB View Download

Sorry I no longer can reproduce it either. Was probably an artifact from upgrading to v64 and disabling autoplay at the same time then restarting Chrome.

Thank you for providing more feedback. Adding requester "susanjunia.boorgula@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Actually I found out the root cause. SpeechSynthesis uses an internal blocking queue from testing, so multiple applications will play one after the other rather than all together (which is a bug I feel too ?).

The problem is with autoplay disabled, Chrome cancels/NOPs the call, but does not clear the queue, so other apps of the API are still stuck in pending.


You can test this by running with autoplay disabled in a console window:
"var utterance = new SpeechSynthesisUtterance('Hello Treehouse');
window.speechSynthesis.speak(utterance);"

Then trying to play SpeechSynthesis on a site.