[BUG]: Inverted Mic icon causes input confusion in Bot Debate Room
维护者通常 1 天内回复
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 70/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- react, typescript, vite
调研方向
从 frontend/src/Pages/DebateRoom.tsx 开始,阅读 isRecognizing 如何控制麦克风按钮和文本区域。检查现有的语音识别行为,然后让图标和表示正在聆听的文字消息与识别状态一致。当空闲和活动状态在视觉上清晰可辨,且文本区域的行为不再令人意外时,即为完成;issue 未指定要运行的测试。
由索引模型根据 Issue 内容生成。
描述
Bug Description
Bug Description :
In the Bot Debate Room (/debate/:roomId), inverted mic icon creates confusion to user :
-
Inverted Mic Iconography
Infrontend/src/Pages/DebateRoom.tsx, the voice toggle button is currently implemented as:<Button onClick={isRecognizing ? stopRecognition : startRecognition}> {isRecognizing ? <MicOff className="w-5 h-5" /> : <Mic className="w-5 h-5" />} </Button>- When speech recognition is active (
isRecognizing === true), it renders<MicOff />, which visually means the microphone is muted for the user. - When speech recognition is idle, it displays
<Mic />, meaning users to think that the app is already listening and mic is active.
- When speech recognition is active (
-
Confusion with
readOnlyInput Locking
The textarea is set toreadOnly={isRecognizing}while speech recognition is active to prevent keyboard conflicts with incoming voice transcripts. But when the user tries to type in when<MicOff />(appearing muted), he gets to know that input is locked, which shows unsynchronized UI defect.
Proposed Solution :
Make the microphone button’s icon match the actual speech‑recognition state and give users a clear written msg that the app is listening, eliminating the confusing read‑only textarea situation.
Steps to Reproduce
- Navigate to Practice with Bot (
/bot-selection) and enter a debate room. - Observe the microphone button before clicking: it shows an active
<Mic />icon even though recognition is idle. - Click the button to start voice recognition: the icon flips to
<MicOff />while the input becomes locked (readOnly). - Attempt to type: input is disabled while the UI appears to show a muted microphone.
Logs and Screenshots
No response
Environment Details
- OS: macOS
- Browser: Chrome (Web Speech API)
- Frontend: React 18, Vite
- Branch:
main(no local modifications aside from temporary dev config)
Impact
Medium - Feature works but has issues
Code of Conduct
- I have joined the Discord server and will post updates there
- I have searched existing issues to avoid duplicates
- 主要语言
- TypeScript
- 星标
- 108
- 派生
- 264
- 平均合并
- 6 小时 53 分钟
- 30 天内合并 PR
- 8
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
AOSSIE-Org/DebateAI 的其他 Issue
-
[BUG]: Duplicate preposition in heading and unformatted feedback text on Strengthen Argument page可能已有人在做 @sujitkr268 于 4 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 72/100
AOSSIE-Org/DebateAI#801 · 2 条评论 ·
维护者通常 1 天内回复
-
[BUG]: Singleton state leak in matchmaking tests causes non-deterministic failures可能已有人在做 @mithunkc017-ship-it 于 8 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 84/100
AOSSIE-Org/DebateAI#798 · 3 条评论 ·
维护者通常 1 天内回复
-
[BUG]: Live Debate Rooms page overflows horizontally on mobile screens可能重新可做 @SYED-IRTEZA-HUSSAIN-RIZVI 于 8 天前认领,目前没有进行中的 PR。 未关闭bug
难度 2/5 1-3 小时 新手友好度 66/100
AOSSIE-Org/DebateAI#797 · 4 条评论 ·
维护者通常 1 天内回复
-
[BUG]: Inconsistent branding on authentication page (Arguehub vs DebateAI)可能重新可做 @SYED-IRTEZA-HUSSAIN-RIZVI 于 8 天前认领,目前没有进行中的 PR。 未关闭bug
难度 2/5 1-3 小时 新手友好度 65/100
AOSSIE-Org/DebateAI#784 · 4 条评论 ·
维护者通常 1 天内回复
-
[BUG]: Coach Service Updates Non-Existent Field (total_points vs score)可能重新可做 @Basharkhan7776 于 27 天前认领,目前没有进行中的 PR。 未关闭bug
难度 1/5 1 小时以内 新手友好度 85/100
AOSSIE-Org/DebateAI#773 · 2 条评论 ·
维护者通常 1 天内回复
查看 AOSSIE-Org/DebateAI 的全部 Issue
相似的 Issue
-
ready-for-agent
难度 1/5 1 小时以内 新手友好度 86/100
LucasSantana-Dev/Lucky#3257 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
danielmiessler/LifeOS#2894 ·
维护者通常 5 天内回复
-
enhancement frontend good first issue help wanted testing-infrastructure
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 2 天内回复
-
enhancement follow-up
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复