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

Demo web-speech-api doesnt work on iOS 16.5 Chrome & Safari & Macbook Pro 13.2 #219

Open
Makio64 opened this issue Jun 1, 2023 · 3 comments
Labels
area: web-speech-api bug A routine task. help wanted If you know something about this, we would love your help!

Comments

@Makio64
Copy link

Makio64 commented Jun 1, 2023

The demo web-speech-api didnt work on iOS 16.5 (iPhone 12 Pro max), I give the permission and the recording is ON but nothing is recognize..

Both Safari & Chrome

It also didnt work on my macbook pro ( OS 13.2 ) Chrome / Safari

@Makio64 Makio64 changed the title Demo doesnt work on iOS 16.5 Chrome & Safari & Macbook Pro 13.2 Demo web-speech-api doesnt work on iOS 16.5 Chrome & Safari & Macbook Pro 13.2 Jun 1, 2023
@caugner caugner added needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. bug A routine task. help wanted If you know something about this, we would love your help! area: web-speech-api and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Oct 10, 2023
@caugner
Copy link
Contributor

caugner commented Oct 25, 2023

Tested the web-speech-api examples in Firefox:

Header Desktop Mobile
phrase-matcher ❌ Fails, console has Uncaught ReferenceError: webkitSpeechRecognition is not defined error. ❌ Fails.
speak-easy-synthesis ✅ Works as expected. ✅ Works as expected.
speech-color-changer ❌ Fails, console has Uncaught ReferenceError: webkitSpeechRecognition is not defined error. ❌ Fails.

The speech-color-changer works in Chrome on Android, but in Chrome on Mac OS I'm always getting Error occurred in recognition: no-speech.

@guest271314
Copy link
Contributor

I think Chrome includes some kind of silence detection algorithm baked in to the implementation of webkitSpeechRecognition(). Additionally since Chrome does not provide a means to select a specific audio device at the prompt it's possible for the audio input device to not be a microphone.

@guest271314
Copy link
Contributor

Keep in mind speech recognition makes a network request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: web-speech-api bug A routine task. help wanted If you know something about this, we would love your help!
Projects
None yet
Development

No branches or pull requests

3 participants