Bug 250665
| Summary: | Regression: SpeechSynthesis.getVoices() no longer lists Kyoko (ja-JP) since iOS 16.0.2 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Takao Baba <baba> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | cfleizach, sihui_liu, tyler_w, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 16 | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 16 | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=290497 | ||
Takao Baba
# Steps to reproduce
1. Open https://eeejay.github.io/webspeechdemos/
# Expected behavior
"kyoko (ja-JP)" is listed on the voice pulldown.
# Actual behavior
"Kyoko (ja-JP)" is not listed on iOS 16.0.2 or later. iOS 16.0 or below seem work well.
Note that the Japanese text still can be spoken on iOS 16.0.2 though there are no Japanese voice.
https://jsbin.com/wiwifayahi/edit?html,js,output
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/104303763>
Takao Baba
I couldn't confirm on my device but my colleague says that enabling VoiceOver sometimes solves the issue.
SpeechSynthesis is widely used for accessibility feature of educational textbook in Japan. This bug breaks at least two reading systems. I'm expecting the fix. Thanks.
chris fleizach
(In reply to Takao Baba from comment #2)
> I couldn't confirm on my device but my colleague says that enabling
> VoiceOver sometimes solves the issue.
>
> SpeechSynthesis is widely used for accessibility feature of educational
> textbook in Japan. This bug breaks at least two reading systems. I'm
> expecting the fix. Thanks.
Ack'd. There were no changes in 16.0.2 that would have caused this, so possible it's intermittent. We'll investigate
Takao Baba
This issue has worsened in iOS 18. Only low-quality "Eloquence" group voices are listed.
I've found some related issues:
https://forums.developer.apple.com/forums/thread/723503
https://developer.apple.com/forums/thread/764438
Alexey Proskuryakov
Thank you for the update. This indeed seems similar to the above forum discussions, and also perhaps to bug 290497. However, multiple people attempted to reproduce, both back in 2023 and now, and we can not.
Could you please file a Feedback Assistant report with a sysdiagnose and a screen recording of reproducing this issue, and post the FB number here?