UI 布局修复：标题栏压缩、滚动条对齐、composer 精简#3589
Conversation
- 标题栏：去掉重复项目名前缀，字号 18px→15px，padding 缩小 - 滚动条：改用 overflow-y:overlay 悬浮不占位，scrollbar-gutter:stable - Composer：移除 caret 符号和 slim input area，send 按钮移入 meta bar - 对话区：composer-card 负 margin 修复左对齐，QuestionJumpBar 固定视口中央 - 其他：隐藏 thinking label，移除 process-card 背景，CSS 变量统一 - gitignore：添加 .alma-snapshots
github-actions
Bot
added
v2
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
DeepSeek-Reasonix/desktop/frontend/src/styles.css
Line 10606 in 52dca87
Restore the command palette rules
The deleted .palette* and .drawer-backdrop:has(.palette) rules are still the only styles for CommandPalette.tsx (confirmed with repo-wide rg for palette__/.palette). Opening the command palette now falls back to the drawer backdrop's justify-content: flex-end and unstyled native buttons/inputs, so the palette appears as an unformatted side-drawer instead of the centered command dialog.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| {!empty && showQuestionNav && ( | ||
| <QuestionJumpBar questions={questions} onJump={handleJumpToQuestion} /> | ||
| )} | ||
| <div className="transcript-wrap"> |
There was a problem hiding this comment.
When there are enough messages to overflow, this new wrapper is the direct child of .main but has no CSS such as flex: 1/min-height: 0/height: 100%; .transcript's height: 100% is now relative to an unconstrained wrapper, so the wrapper expands to content while .main has overflow: hidden. That leaves the scrollRef element without the intended viewport-sized scrollbar and can make older/newer messages inaccessible behind the footer.
Useful? React with 👍 / 👎.
| <button | ||
| className="composer-meta__action-btn composer-meta__action-btn--send" | ||
| onClick={submit} |
There was a problem hiding this comment.
The send/stop button was moved from .composer__btn--send to the new .composer-meta__action-btn* classes, but a repo-wide search shows no CSS rules for those classes. In the normal non-running composer this makes the primary send control fall back to native button styling/metrics instead of the fixed square primary action, which is a visible regression in the composer layout.
Useful? React with 👍 / 👎.
| background: var(--sidebar-hover); | ||
| color: var(--fg); | ||
| } | ||
| .workspace-tree__chev { |
There was a problem hiding this comment.
This deletion removes the only .workspace-git-history* styles while WorkspacePanel.tsx still renders those classes in the changed-files history view. When users open the changed/history pane, commit headers and file rows now revert to native button layout and the expanded details lose their spacing/borders, which makes the git history UI visibly broken and harder to use.
Useful? React with 👍 / 👎.
| {(turnTokens ?? 0) > 0 && ( | ||
| <span className="statusbar__tokens">↓ {fmtTokens(turnTokens ?? 0)} {t("status.tokens")}</span> |
There was a problem hiding this comment.
After any turn that reports usage, turnTokens remains at the last turn's value until the next turn starts, but this condition renders it whenever it is greater than zero. Previously the token count was part of the running-only activity text, so the status bar now shows a stale per-turn token total after completion, which is misleading while the app is idle.
Useful? React with 👍 / 👎.
| ready={state.meta?.ready === true} | ||
| turnStartAt={state.turnStartAt} | ||
| turnTokens={state.turnTokens} | ||
| retry={state.retry} | ||
| workspaceRefreshSignal={projectRevision} |
There was a problem hiding this comment.
The controller still stores backend retrying events in state.retry, but these removed props were the only consumer of that state (confirmed with repo-wide rg for state.retry/retry). During API retries the UI now only shows the generic spinner, so users lose the explicit retry attempt/max indication and cannot tell that the app is retrying rather than simply hung.
Useful? React with 👍 / 👎.
|
给一个效果图看看 |
2 participants
UI 布局修复
标题栏
滚动条对齐修复
Composer 精简
其他