fix(kimi-web): keep composer toolbar usable on narrow windows - #1436
Conversation
🦋 Changeset detectedLatest commit: b126623 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
![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
Here are some automated review suggestions for this pull request.
Reviewed commit: 80c05aeec7
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| .ctx-num { | ||
| display: none; | ||
| } |
There was a problem hiding this comment.
When the viewport is ≤980px, display: none removes the only textual representation of context usage. The remaining ContextRing SVG is aria-hidden, and the tooltip is only shown from hover/focus listeners on a non-focusable span, so keyboard and screen-reader users on narrow desktop/mobile layouts can no longer get the used/max/pct value. Keep this text visually hidden instead, or add an accessible label to the ring/trigger when the visible count is suppressed.
Useful? React with 👍 / 👎.
The desktop composer toolbar renders every control on one row and relies on overflow:hidden to fit, so between the mobile breakpoint and a wide window it clipped its own content. Shed secondary ink below 980px (the context readout moves into the ring tooltip, the model name truncates earlier, permission is capped) and keep the context ring visible on phones too, instead of sending it to the settings sheet.
80c05ae to
b126623
Compare
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback". |
1 participant
Related Issue
No linked issue — this is a small responsive-layout fix for the web composer found while tightening the toolbar at small widths.
Problem
The composer bottom toolbar lays every control on a single flex row, and its left / right halves use
overflow: hiddento make them fit. Between the mobile breakpoint (640px) and a wide desktop — especially with the sidebar open, or on a phone — the row clipped its own content: the context readout, the model name, and the permission pill were cut off, and the context ring was hidden entirely on phones even though it is the live context-pressure signal.What changed
12k/256kcontext readout (still available in the ring tooltip), cap the model name at 130px, and cap the permission pill at 104px with ellipsis, so the context ring and send button are no longer squeezed out on a narrow column.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.