[Bug]: Chat text shows in the empty gap below the composer

Offen Anfängerfreundlich
#39,110 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
66/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
css, typescript
Bereich
frontend

Rechercherichtung

Beginne bei den Chat-Timeline- und Composer-Stilen in apps/web; das Issue weist auf einen fertigen CSS-Fix mit zwei Dateien im Fork des Meldenden hin. Lies die Spacer- und Scroller-Stile und vergleiche anschließend das vorgeschlagene Clipping-Verhalten und dessen Auswirkungen auf das Hit-Testing. Fertig ist die Arbeit, wenn beim Scrollen der Nachrichten kein Text mehr in den Bereich unter dem Composer gezeichnet wird und die erwarteten Hintergründe sowie das Glaselement des Composers intakt bleiben.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug needs-triage

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
  1. Open a thread with enough messages to scroll. Leave "Keep composer context visible" off (the default).
  2. Scroll up until a message passes under the composer.
  3. 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.

Desktop app: message text below the composer

Before: message text below the composer. After (proposed fix): the gap stays empty

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

Before and after in dark, light and a theme with a conversation background

Before and after at 1920×1080, 1440×900, 1024×768 and 768×1024

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-path also 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).

Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
4 Std. 46 Min.
Gemergte PRs (30 T.)
488

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.