Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Allow candidates to toggle avatar visibility back on (Show/Hide Avatar)

未关闭
#291 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust, web-dev

调研方向

Start by locating the #hide-avatar button, startAvatar(), attachAvatarAnalyser, and the avatarDisabled state mentioned in the issue. Trace the hide and stopped flows, then check how jimTrack is managed and how the interface announces toggle changes. Done means candidates can hide and restore the avatar without refreshing, with teardown preserved and keyboard focus and announcements handled.

由索引模型根据 Issue 内容生成。

描述

Problem / Motivation
Currently, clicking the "Hide avatar" button permanently disables the avatar for the remainder of the session, destroys the WebGL/AudioContext resources, and hides the button itself.

If a candidate accidentally clicks "Hide avatar" or decides later in the interview that they would like to bring Jim’s avatar back, there is currently no way to re-enable it without refreshing the page.

Proposed Solution
Transform the single-use "Hide avatar" button into a toggle button ("Hide avatar" / "Show avatar"):

Button State Management: Instead of hiding #hide-avatar on stopped state, keep the button visible and update its text content to "Show avatar".

Re-initialization Flow: When clicked while hidden, clear the avatarDisabled lock and invoke startAvatar(). Re-attach the audio analyser (attachAvatarAnalyser) if jimTrack exists.

Resource Efficiency & Accessibility: Maintain full WebGL/analyser teardown on hide to preserve performance benefits, while maintaining proper keyboard focus and accessibility announcements when toggled.

If this issue is accepted I would like to deal with it.

主要语言
Rust
星标
160
派生
64
平均合并
1 天 9 小时
30 天内合并 PR
103

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

sysprog21/codetrial 的其他 Issue

查看 sysprog21/codetrial 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。