Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SpeechSynthesis breaks in Chromebooks when switching tabs #64

Closed
jessegreenberg opened this issue Feb 25, 2022 · 3 comments
Closed

SpeechSynthesis breaks in Chromebooks when switching tabs #64

jessegreenberg opened this issue Feb 25, 2022 · 3 comments

Comments

@jessegreenberg
Copy link
Contributor

Here is the initial issue where this was discovered: phetsims/number-play#138

@jessegreenberg
Copy link
Contributor Author

In #66 we added the ability to detect this failure case in ChromeOS.

If the amount of time between setting the pendingUtterance and the start event is greater than PENDING_UTTERANCE_DELAY we can assume there has been a failure of the engine and we cancel speech and remove listeners before the next attempt to speak.

Hopefully we can find a way to fix it when this happens. Potentially by trying to add it to the back of the queue again until we have a success?

@jessegreenberg
Copy link
Contributor Author

Actually, the behavior seems quite a bit better now that we have a cancelSynth() when we detect the failure case. After this cancel, speech consistently resumes after a couple of seconds. So ~8 seconds after you return to the tab Voicing will start working again.

This seems acceptable to me and I don't think it is worth debugging further. We could try to add the failed Utterance back to the front of the queue but I am worried about an infinite loop of failed announcements and adding more complexity just for this ChromeOS case.

Lets see if the issue is largely resolved over in phetsims/number-play#138 and then possibly just close.

@jessegreenberg
Copy link
Contributor Author

phetsims/number-play#138 was verified as improved. That is all we will do on this issue for now. I updated the "Accessibility bugs" markdown file in QA to describe what we expect from ChromOS. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant