fix(music): autoplay rejections are only logged and never retried

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
72/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript

调研方向

Start with the rejection handlers at modules/music/src/music.library.ts:70-73 and modules/sound/src/sound.library.ts:62-64, then trace how music starts in main and how input events are registered. Check existing tests around playback and input handling, or add coverage for AbortError and NotAllowedError. Done means aborted switches are not logged as errors and blocked music retries after the first pointerdown or keydown.

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

描述

bug modules:music modules:sound
Which package is this bug report for?

music

Issue description

A NotAllowedError (autoplay blocked before a user gesture) is only logged as Got error: …, and _current points to a track that is not playing, so menu music started in main stays silent for the whole session. An expected AbortError (switching tracks quickly) is logged as an error too.

Where:

Evidence:

this._current.play().catch((error: unknown) => {
  console.error(`Got error: ${error}`);
});

Suggested fix: Ignore AbortError. On NotAllowedError, keep the pending track and retry on the first pointerdown / keydown.

Found during a code audit of main at be72076.

Code sample

No response

Versions
  • Engine main at be72076
  • pnpm 12.0.0, Node.js 26, Bun 1.3.14
Issue priority

Medium (should be fixed soon)

I have tested this issue on a development release

be72076

主要语言
TypeScript
星标
7
派生
2
平均合并
1 天 17 小时
30 天内合并 PR
17

环境准备

从这里开始

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

NanoForge-dev/Engine 的其他 Issue

查看 NanoForge-dev/Engine 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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