Answer shortcut vanishes on a narrow frame
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by locating taskPaneCols, taskPaneOpen, taskPaneKey, and taskRecordAnswer, then run the replication recipe in a terminal narrower than 110 columns. Check the tasks list and the record card using the digit and enter. Done means the narrow list either accepts the answer key directly or visibly tells the user how to answer, verified end to end on the real surface.
由索引模型根据 Issue 内容生成。
描述
What happens
Below a frame width of 110 cells the tasks list draws no side pane, and with no pane the answer keys the pane offers are not bound. taskPaneCols returns zero under the floor, taskPaneOpen reports false from it, and taskPaneKey returns early on !a.taskPaneShowing(), so a digit that names an answer does nothing from the list.
What is NOT wrong, checked before filing
The answer road still exists at any width. enter from the list opens the record card, and the card reaches the same door (taskRecordAnswer) that the pane reaches, by the comment's own statement that a second loop over the options there would be a second chance for the two to disagree about what 1 means.
So this is one extra keystroke on a narrow terminal, not an unanswerable question. An earlier reading of this as "the page has no door below 110 columns" was wrong and is corrected here.
Why it is still worth deciding
- The verb line that advertises the keys is drawn by the pane, so on a narrow frame a person is not told the shortcut is unavailable; it is simply absent. Nothing says "press enter to answer".
- Nobody has established whether the record card itself renders usefully below 110 cells. That is unverified and is the question that decides whether this is cosmetic or real.
The decision wanted
Either: accept the floor, and make the narrow list say how to answer, so the absence is announced rather than silent.
Or: bind the answer keys on the list itself at any width, so the shortcut does not depend on a layout choice.
The first is smaller and consistent with the floor's stated reasoning, which is that under 110 cells a split buys a preview by making the thing previewed unreadable.
Replication
NOT YET RUN. Recipe a stranger can execute: open the tasks place in a terminal narrower than 110 columns with a row whose work is waiting on an answer, and press the digit the wide frame would accept. Then press enter and the same digit on the card.
Acceptance
End to end, at a frame under the floor: the list either accepts the answer key directly, or draws a line naming the key that does. Asserted on the real surface, not on a width helper.
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 9 小时 35 分钟
- 30 天内合并 PR
- 752
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Agent-Field/CodeAF 的其他 Issue
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 86/100
Agent-Field/CodeAF#1592 ·
维护者通常 1 天内回复
-
area:headless bug sev:critical
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1566 ·
维护者通常 1 天内回复
-
area:chat bug sev:critical
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1548 · 1 条评论 ·
维护者通常 1 天内回复
-
area:chat feature
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1510 ·
维护者通常 1 天内回复
-
area:tests bug
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1489 ·
维护者通常 1 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 1/5 1 小时以内 新手友好度 65/100
521xueweihan/HelloGitHub#3789 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 12 天内回复
-
stage-fail
难度 2/5 1-3 小时 新手友好度 78/100
siyuan-note/bazaar#2282 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
openshift/kube-compare#307 ·
维护者通常 1 天内回复