[Bug]: Chat text shows in the empty gap below the composer
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, typescript
- Domain
- frontend
Research direction
Start in the apps/web chat timeline and composer styles; the issue identifies a ready two-file CSS fix on the reporter’s fork. Read the spacer and scroller styles, then compare the proposed clipping behavior and its hit-testing trade-off. Done when scrolling messages no longer paints text in the gap below the composer while the expected backgrounds and composer glass remain intact.
Written by the indexing model from the issue text.
Description
Hi! This is my first issue here. First, I'm really loving the app! But the text below the chat box really irks me. I first thought about making a PR, but since this is not clearly a bug, as it could be a design choice given the current maintainer's position, I settled on an Issue. For me personally, it's not pretty and also not very useful (the text lacks its context).
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
- Open a thread with enough messages to scroll. Leave "Keep composer context visible" off (the default).
- Scroll up until a message passes under the composer.
- Look at the gap between the bottom of the composer card and the bottom of the window.
Expected behavior
The gap below the card stays empty, as it does when nothing is behind it.
Actual behavior
Message text renders in that gap, detached from the card and the conversation.


This is not about the glass behind the card (#13955, #22227), only the empty spacer under it.
#34846 fixed this under the context row (#27512) but kept the spacer transparent: "it matches the setting-off behavior and covers no labels." With the setting off (the default), the spacer is all there is under the card.
Related: #30048 (closed as a duplicate of #27512), #29975 and #30064 (closed unmerged). Not #12937, which was a seam inside the composer.
Impact
Cosmetic issue
Version or commit
main at 475ae52.
Environment
Linux. Seen in the T3 Code desktop app and reproduced in the web dev client (Chromium) with a synthetic project and a Replay (dev) thread. Same in light, dark and a theme with a conversation background.
Logs or stack traces
Screenshots, recordings, or supporting files


A possible fix is ready on my fork (2 files, CSS only): https://github.com/j6e/t3code/compare/main...fix/composer-bottom-gap
- The spacer's height moves into one variable,
--chat-composer-spacer-height. The timeline scroller is clipped by that height, so it never paints in the gap. Nothing is painted over it, so any theme background shows through, and the glass behind the card is unchanged. - Optional refinement on the same branch: the clip also rises by the card's corner radius (
--radius-2xl). Cut exactly at the gap, a glyph sliced at that edge leaves a speck on the rounded corner; the cost is that the lowest 16px of glass have nothing behind them to blur. It can be dropped if you'd rather keep the glass fully untouched. - Known trade-off:
clip-pathalso clips hit-testing, so the mouse wheel does nothing in that bottom strip beside the composer. Under the composer the wheel never scrolled the timeline anyway.
If this is worth fixing, I can open it as a PR with the full verification.
Workaround
None found. Glass opacity at 100% makes the card opaque, but the text in the gap stays (capture).
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 4h 46m
- Merged PRs (30d)
- 488
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
[Bug]: Add provider can create a built-in driver's default instance, which has no delete actionPossibly taken @nateEc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#38462 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day
-
Progress indicated by console logs is off by onePossibly taken @marceliwac claimed this today. Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/aws-cdk-examples#1336 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#4999 · 1 comment ·
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
db-ux-design-system/core-web#8856 ·
Maintainers usually reply within 1 day