Skip to content

Commit 97dd9a0

Browse files
authored
Merge pull request #550 from CWNU-Open-Source-Community/Qiyuanqiii/overnight-chat
fix(web): 保持待处理消息编辑时的聊天输入框可见
2 parents 7705a45 + f0f8992 commit 97dd9a0

20 files changed

Lines changed: 188 additions & 7 deletions
Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
# Queued-message editing — 2026-11-07
2+
3+
Base: `cfeee05a8724a23c673b0ed9971f2ef6e8de9674`.
4+
5+
Opening three queued-message editors made the recovery area grow without a
6+
height limit. At 1280 × 800, the transcript shrank to zero height and the ordinary
7+
composer started at y=871.8, below the viewport. Reloading restored the editors
8+
and the same obstruction.
9+
10+
The message list, editors and unconfirmed operations now share one scroll area,
11+
bounded by 220px or 26% of the viewport height while edits are open. The composer
12+
stays outside it. Editor controls, collapsed-list recovery access and stored
13+
draft identities are preserved. Opening an editor focuses it and scrolls it
14+
into the shared area.
15+
16+
In the reproduced stopped-task scenario, the patched 1280 × 800 layout keeps
17+
231px of transcript visible and the composer ends at y=787. At 390 × 844 the
18+
composer ends at y=834, with no horizontal page overflow. All three local edits
19+
remain available by scrolling, and survive reload alongside the ordinary draft.
20+
21+
## Official product references
22+
23+
The [Claude Code Desktop prompt-box reference](https://code.claude.com/docs/en/desktop#use-the-prompt-box)
24+
documents stopping immediately and sending corrections while an action runs.
25+
The [Codex long-running-work reference](https://learn.chatgpt.com/docs/long-running-work)
26+
documents follow-up messages that adjust an ongoing task. These established
27+
workflows motivated checking whether queued corrections remain usable here.
28+
This report makes no claim that either product lacks an undocumented feature.
29+
30+
## Real browser captures
31+
32+
These are unmodified viewport screenshots from Windows Chromium: desktop
33+
1280 × 800 and narrow 390 × 844, using the application's Light and Dark settings.
34+
The base bundle was served by the real Go journey API. The patched production
35+
bundle was served by Vite preview, proxying that same API. Editors were opened
36+
and filled through the UI in each origin. No HTTP responses or rendered content
37+
were mocked. The existing unavailable-browser notice was dismissed in both
38+
versions. The separate automated journey below serves the patched bundle
39+
directly through Go.
40+
41+
| Theme / viewport | Before | After |
42+
| --- | --- | --- |
43+
| Light / desktop | [Before](../images/queued-message-editing/before-light-1280.png) | [After](../images/queued-message-editing/after-light-1280.png) |
44+
| Dark / desktop | [Before](../images/queued-message-editing/before-dark-1280.png) | [After](../images/queued-message-editing/after-dark-1280.png) |
45+
| Light / narrow | [Before](../images/queued-message-editing/before-light-390.png) | [After](../images/queued-message-editing/after-light-390.png) |
46+
| Dark / narrow | [Before](../images/queued-message-editing/before-dark-390.png) | [After](../images/queued-message-editing/after-dark-390.png) |
47+
48+
## Short-window follow-up
49+
50+
The first fix capped the message list and recovery editors separately. That
51+
still exhausted the chat height in short windows. The desktop's declared
52+
minimum is 480 × 600 (`cmd/cyberagent-desktop/main.go`); the 390 × 500 case below
53+
also checks the browser layout at a shorter height.
54+
55+
| Viewport | Transcript before → after | Composer bottom before → after | Screenshots |
56+
| --- | --- | --- | --- |
57+
| 1280 × 600 | 0 → 83px | 614 → 587px | [Before](../images/queued-message-editing/short-before-1280x600.png), [After](../images/queued-message-editing/short-after-1280x600.png) |
58+
| 480 × 600 | 3 → 123px | 590 → 590px | [Before](../images/queued-message-editing/short-before-480x600.png), [After](../images/queued-message-editing/short-after-480x600.png) |
59+
| 390 × 500 | 0 → 49px | 561 → 490px | [Before](../images/queued-message-editing/short-before-390x500.png), [After](../images/queued-message-editing/short-after-390x500.png) |
60+
61+
The earlier two-region layout is shown in these short-window Before captures.
62+
The After captures use the same actual Thread and queued messages, with editors
63+
opened through the patched UI. All three editors remain reachable by keyboard
64+
focus and scrolling. The queue menu ignores a deferred scroll event when its
65+
anchor has already been positioned at that location, and still closes when the
66+
anchor moves.
67+
68+
## Verification
69+
70+
- `npm run build`: passed strict TypeScript and the production bundle.
71+
- `npm test -- --maxWorkers=2 src/v2/components/queued-messages.test.tsx src/v2/queue-recovery.test.ts`:
72+
40 tests passed.
73+
- `WORKBENCH_JOURNEY_SKIP_BUILD=1 npm run test:journeys -- --grep "queued message edits"`:
74+
one production Go/Chromium journey passed. It queues five messages, stops the
75+
current turn, edits three messages, reloads, checks five viewport sizes through
76+
the desktop minimum and shorter browser height, focuses every retained editor,
77+
and saves one edit while the message list is collapsed.
78+
The ordinary composer draft stays intact.
79+
- `git diff --check`: passed.
80+
81+
The journey uses the repository's offline model provider to hold an actual
82+
runtime turn. No external model service was called. Initial runs encountered a
83+
changing active-turn layout and the existing browser notice reappearing after
84+
reconnect. The final journey stops the turn and waits for and closes that notice
85+
before measuring the queue. It retains the original transcript-height assertion.
86+
87+
OCR delegate selected the three production files and excluded tests by its
88+
default path rules. CSS was read in full; the TSX and browser spec were read
89+
around the changed QueuePanel/QueueEditor/QueueMessageMenu paths, journey and
90+
surrounding helpers. The new scroll-event regression was read in full. No finding
91+
remains in this patch. Unrelated application files were read only as needed for
92+
the flow.
107 KB
Loading
56.8 KB
Loading
117 KB
Loading
56.4 KB
Loading
102 KB
Loading
53.4 KB
Loading
111 KB
Loading
52.5 KB
Loading
100 KB
Loading

0 commit comments

Comments
 (0)