Repository navigation
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Responsive layout and validation packages/ui/src/styles.ts, packages/ui/test/appearance.test.ts, CHANGELOG.md |
The Inbox uses a named inline-size container, a 240px minimum list-column width, and container queries at 559px and 1023px. The narrow layout styles the Back button. The test checks the container and queries, and the changelog records the layout changes. |
Snippet source metadata scripts/doc-snippets/recipes.mjs, contracts/doc-snippets.json |
The recipe source commit and the manifest’s source commit and source-files SHA-256 values are updated. |
Priority:
Estimated code review effort: 2 (Simple) | ~10 minutes
Change: Bug fix
Merge Risk: 
acdfc
-
No actionable merge-blocking issue is established for these changes. Merge after normal checks.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly and concisely summarizes the main Inbox layout and Back-button changes. Description check The description includes Summary, Verification, and Release status sections. It explains the behavior changes, validation results, known date-dependent test failure, and nightly publication issue. Docstring Coverage No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 3… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 3 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
![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: 9b965da7ab
ℹ️ 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".
| position: relative; | ||
| display: grid; | ||
| grid-template-columns: minmax(280px, 380px) minmax(0, 1fr); | ||
| grid-template-columns: minmax(240px, 380px) minmax(0, 1fr); |
There was a problem hiding this comment.
At the newly supported 560–699px Inbox widths, the first grid track expands to 380px before the 1fr track receives the remaining space. A 560px content box therefore gives the thread only 180px, not the 320px stated in the new comment. The existing thread header must fit its avatar, contact action, padding and gaps into that space, severely truncating the contact identity and squeezing messages and the composer; previously these widths displayed a full-width thread. Cap the list relative to the available width or otherwise reserve 320px for the thread before enabling the two-pane layout.
Useful? React with 👍 / 👎.
… when it cannot The Inbox's layout rules used unnamed container queries. The thread pane is a container too, so the rule that shows Back read the thread's width and Back appeared beside the list in the two-pane layout. The Inbox's container is now named and its rules query it. The list and the thread sit side by side from 560px of Inbox width (was 700px); the list's minimum is 240px, leaving the thread 320px. Back has a visible border where it shows.
acdfc79 to
fbc7a00
Compare
Summary
Verification
@polymorfa/ui,@polymorfa/reactand@polymorfa/elements: 207 of 208 tests pass, typecheck, eslint and prettier pass.react.test.tsx"renders attachments, reply quotes, date separators, and status". It is date-dependent: run locally on 2026-10-25 in EET, the night clocks went back, the messagenow - 2 * 86_400_000falls on yesterday's date. Nothing in this change touches it.Release status
Source only. It reaches npm with the next nightly. The nightly publish has failed on every run since Oct 21: the workflow's GitHub App client ID is not set.
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by CodeRabbit