-
Notifications
You must be signed in to change notification settings - Fork 2
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
Can we remove safariWorkaroundUtteranceWrappers from voicingManager? #52
Labels
Comments
From #43 (comment) |
jessegreenberg
added a commit
that referenced
this issue
Jan 28, 2022
jessegreenberg
added a commit
to phetsims/scenery
that referenced
this issue
Jan 28, 2022
jessegreenberg
added a commit
to phetsims/scenery
that referenced
this issue
Jan 28, 2022
I removed the workaround array. Unit tests are passing in Chrome, Firefox and Safari. I was not able to produce the bug in phetsims/john-travoltage#435 in Safari after this change. So I think we are in the clear. @zepumph since this came from #43 (comment), would you recommend anything else? |
Looks so great. Thank you! |
Great, thanks! |
jessegreenberg
added a commit
that referenced
this issue
Feb 7, 2022
jessegreenberg
added a commit
that referenced
this issue
Feb 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
voicingManager currently lives in scenery but I am putting this issue here because it came from #43 and because this issue is part of a collection of other utterance-queue work. And SpeechSynth code may soon move to this repo anyway see #34.
@zepumph said
Earlier today we tried to remove them by removing the
end
event listeners entirely in phetsims/scenery#1344 and couldn't get it to work. But we may still be able to get rid of the safari workaround list because the reference to the speaking utterance is in the speakingSpeechSynthesisUtteranceWrapper.Here is the bug that made the workaround necessary - phetsims/john-travoltage#435. if this is not reproducible and the sims behave well I think we can consider it safe to remove.
The text was updated successfully, but these errors were encountered: