web-speech-api example does not use microphone input from bluetooth source when connected
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 7h 53m
- Merged PRs (30d)
- 1
Description
What information was incorrect, unhelpful, or incomplete?
When testing the "Phrase matcher demo" of the web-speech-api,
https://github.com/mdn/dom-examples/tree/main/web-speech-api#phrase-matcher-demo
On an Android device with the Chrome browser,
When a bluetooth headset is paired and connected to the device, it does not use this bluetooth mic as expected:
What did you expect to see?
Observed behaviour:
Audio input is still routed to Chrome via the on-device mic.
Expected Behaviour:
Audio input should be routed to Chrome via the connected bluetooth mic.
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
Other observations:
Audio input is routed via the connected bluetooth mic for phone calls.
Audio output works as expected and is correctly routed from the Chrome browser to the bluetooth headset spekers.
Audio input works as expected when using a wired headset - the microphone from the wired headset is used as audio input when conected.
Android version: 14; SM-G556B Build UP1A.231005.007
Chrome version: 129.0.6668.100
Headset: Jabra Evolve 65
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Phrase matcher demo at the linked web-speech-api path and reproduce it on Android Chrome with the specified Jabra Bluetooth headset. Determine whether the behavior is caused by the example or by browser/platform microphone routing; done means the example uses the connected Bluetooth microphone or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100