Repository navigation
Conversation
…crolling Top-level tables in assistant replies now widen into the timeline's side gutters (centered, capped to the pane minus the minimap gutter). The horizontal scroll view only kicks in when even the full pane is too narrow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This is a localized web UI adjustment that changes how assistant markdown tables use available timeline width while preserving the existing scrolling fallback and table controls. It introduces no schema, deployment, security, billing, or configuration changes. You can add or adjust custom eligibility rules. Learn more. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: pingdotgg/t3code/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughAssistant markdown tables no longer have expand and collapse controls. Their cells always wrap. The assistant timeline opts into wide-table styling, which sizes the table frame against the timeline container and caps its width at 64rem. ChangesAssistant table layout
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to No actionable merge-blocking issue remains. Wide assistant tables can use the wider frame while other inspected content stays bounded. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 2 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…idth The expand/collapse cell toggle is gone: cells always wrap at 24rem now that tables can widen. The breakout is capped at 64rem so tables scroll sooner, and the flex wrapper no longer stretches the frame, which had let the ScrollArea swallow the copy footer and overlap the following text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…antTimelineRow Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Cool! I'm here because it's annoying to scroll sideways when there's still space left on my screen. But why 64rem as the limit? I like the approach of #11594, but I don't want the whole chat to be wide, I only want huge tables to be wide. |
|
I added that limit because I didn't want the table to occupy the whole width. It felt a little bit weird. Either way, I don't think they will merge with BR. |
|
Note This comment is posted by Julius' dot This changes the default table layout and removes the existing expand/collapse control. No maintainer approval for that direction is linked. Closing under prior approval. The wasted space around wide tables is useful feedback; please agree on the layout and controls in Ideas, then link that approval for reconsideration. |
What Changed
justify-content: center), not transforms, so text stays pixel-snapped. The timeline scroll element is a size container (@container/chat-timeline) so the cap can use the pane width..chat-markdown-wide-tables) widen. Tables inside lists, blockquotes, reasoning, user messages, and cards stay in the column.overflow-x-clipso the wider table can paint. The list's ownoverflow-x-hiddenand LegendList's per-itemcontain: paintstill clip at the pane edge.Surfaces: web and desktop share this path. Mobile uses its own native markdown renderer and is unchanged.
Why
Markdown tables in assistant replies were capped to the reading column. Any table with more than a few columns got a horizontal scroll view and truncated cells, even when the chat pane had plenty of empty space on both sides. Letting tables use a bounded amount of that space makes most comparison tables readable at a glance. The scroll view stays as the fallback for very wide tables. Once cells wrap by default, the expand toggle has nothing left to do, so it's removed rather than kept as a dead control.
UI Changes
Before: the table is limited to the reading column, cells truncate, and it scrolls horizontally.
After: the table widens past the column (up to 64rem), cells wrap, and there's no expand toggle.
Checklist
🤖 Generated with Claude Code (Claude Opus 5.5)
Summary by CodeRabbit
Improvements
Changes