mirrors/pikasTech-HWLAB
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: keep quick prompts in composer flow

Browse Source
This commit is contained in:
Codex
2026-05-26 02:24:45 +08:00
parent cdb70b12b2
commit 78da29d781
3 changed files with 6 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/cloud-workbench.md
+4 -3
View File
@@ -45,9 +45,10 @@ runtime summaries, live-build indicators, dialogs, and status chips may report
context, but they must never cover or intercept clicks intended for the command
composer, Code Agent input, send controls, or quick-prompt buttons. If a fixed
or visually persistent status surface can overlap after `scrollIntoView`, mobile
reflow, or trace updates, the composer layer must win the stacking order and
non-interactive summary text must not become a pointer target. Layout/browser
smoke should treat this as a real hit-target failure, not as a test flake.
reflow, or trace updates, the command composer must keep quick prompts inside
its own flow below the primary input controls, and non-interactive summary text
must not become a pointer target. Layout/browser smoke should treat this as a
real hit-target failure, not as a test flake.
The left resource explorer is a controlled resizable column on desktop-class
viewports. Its width defaults to `292px`, clamps inside a bounded range