Machine menu in the Chat box is cut off at the bottom right once the workspace has documents
维护者通常 1 天内回复
@lavaman131 已经在做这个了。
开始于 2026年10月16日。
评估
这个 Issue 还没有评估数据。
描述
The machine button's menu, at the bottom right of the Chat box next to Send, is cut off at the bottom of the window once the workspace has documents. Its lower rows can't be reached. With a completely empty workspace the same menu opens fully.
Steps to reproduce
- Sign in with at least one paired machine, so the machine button shows in the Chat box.
- Add one or more documents to the workspace, so the sidebar lists projects or documents.
- Open a document and click the machine button at the bottom right of the Chat box.
Expected: the whole menu is visible: Default machine, each machine, and Add machine…. If there isn't room below, it opens upwards, or scrolls inside itself (the behaviour added in #639).
Actual: the menu runs past the bottom right edge of the window and its lower rows are clipped, with no way to scroll to them.
Works: the same steps in a completely empty workspace show the whole menu.
Notes
- #639 made the machine menus fit the window and scroll inside. Its e2e test measured them with 12 machines at 1280x600 and 390x844, but with an empty workspace. The clipping only appears once the workspace has content, so something that content adds is likely constraining the menu. Possibilities to check:
- a different scroll container or overflow on the document layout;
- a transform or containing block that breaks the menu's fixed positioning;
- the space check measuring against the wrong element.
- Fix: reproduce with real sidebar content, then extend the e2e test so it runs with a populated workspace as well as an empty one.
Assistant-workflow: inline
Assistant-duration: unmeasured
Assistant-verification: manual unavailable: reported by lavaman131 on the hosted instance; not reproduced locally yet
Co-authored-by: lavaman131
- 主要语言
- TypeScript
- 星标
- 406
- 派生
- 24
- 平均合并
- 12 小时 42 分钟
- 30 天内合并 PR
- 416
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
githubnext/chopin 的其他 Issue
-
documentation triage/human-response
难度 2/5 1-3 小时 新手友好度 74/100
githubnext/chopin#149 · 3 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 3/5 半天 新手友好度 45/100
githubnext/chopin#597 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 30/100
githubnext/chopin#596 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 12/100
githubnext/chopin#595 ·
维护者通常 1 天内回复
-
enhancement triage/human-response
难度 4/5 3-5 天 新手友好度 55/100
githubnext/chopin#203 · 2 条评论 ·
维护者通常 1 天内回复
查看 githubnext/chopin 的全部 Issue
相似的 Issue
-
bnv-manager-v2: accept_invite creates the Mailcow domain admin before the commit可能已有人在做 @myOmikron 今天认领。 未关闭bug ready-for-agent
难度 2/5 1-3 小时 新手友好度 82/100
-
platform:windows tool triaged wontfix
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
nicolettas-muggelbude/RechnungsFee#448 ·
维护者通常 1 天内回复
-
Android bug feature/error-tracking react-native team/error-tracking
难度 2/5 1-3 小时 新手友好度 72/100
PostHog/posthog-js#5310 · 1 条评论 ·
维护者通常 1 天内回复