-
Notifications
You must be signed in to change notification settings - Fork 1
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
Edge on Android returns an empty voice list #20
Comments
I can't even get to work to build in Read out loud to work on many Edge version and Android Version combinations, and immersive Reader can't read anything as well. That sad thing about it, it was working fine with feature parity to Edge Desktop https://www.youtube.com/watch?v=H5uMaU5inxQ Edit: Read out loud execution and voice selection only breaks on sites with TTS. That's why it feels so random. |
I fixed Edge for me. I did manage to figure out how you can avoid the bug: never call "getVoices()" before Edge Android did initialize the Speech stuff. I used the ReadOutLoud feature: So I set a script stop breakpoint and clicked on ReadOutLoud. The debugger did show me some internal JS code loaded directly from the Android Edge browser. It does some initialization things, but I can't reach all these browser internals. At the end of the week, I will add a version which only presents the workaround if edge is still broken. But it likely needs a page reload since I don't find any clue outside of calling getVoice(). And after calling getVoice() in the broken state, you need a page reload. |
Based on what you're saying, this is enough to lower the severity from critical (can't be fixed) to major. Fun fact: I'm also a PSVR2 owner, I have quite an extensive library of VR titles on it! |
I don't know why I didn't get the onvoiceschange event. Today everything is fine. Which means you don't need a button. |
On Android, the mobile version of Edge returns an empty list of voices when calling
getVoices
.This is our first critical bug reported through this project, as it makes it impossible to implement read aloud on this browser.
Link:
Also related:
The text was updated successfully, but these errors were encountered: