AOSSIE-Org / AOSSIE-Org/DebateAI
[BUG]: Speech Recognition stops automatically despite continuous mode enabled
- Dominant language
- TypeScript
- Stars
- 84
- Forks
- 198
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
### Bug Description
Problem Description
When using the Web Speech API (SpeechRecognition / webkitSpeechRecognition) with recognition.continuous = true, speech recognition still stops automatically after a short period of silence or inactivity.
This behavior breaks the expected continuous listening functionality, as recognition should remain active until it is explicitly stopped by the application.
Steps to Reproduce
1. Initialize SpeechRecognition
2. Enable continuous mode
3. Start recognition
4. Wait for silence or inactivity
5. Recognition stops automatically
Expected Behavior
Recognition should continue listening until manually stopped.
Actual Behavior
Recognition stops automatically due to silence, timeout, or internal browser reset.
Environment
1. Browser: Chrome / Edge
2. Frontend: TypeScript web application
3. API: Web Speech API
Workaround
Restart recognition manually inside the onend event.
### Steps to Reproduce
_No response_
### Logs and Screenshots
_No response_
### Environment Details
_No response_
### Impact
Critical - Application is unusable
### Code of Conduct
- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates
Contributor guide
No contributing guide indexed for this repository
Research direction
No project files or tests are named. Start by locating the SpeechRecognition integration and its onend handler, then reproduce the Chrome/Edge silence behavior with continuous mode enabled. Done means recognition remains usable during silence or the issue documents a verified browser limitation and an appropriate application-level outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100