Skip to content

[Bug]: Text box and text rendering fails when rendered over an image #13955

Description

@dkritarth

Description

When an image in the timeline is scrolled underneath the composer overlay docked at the bottom of the timeline, text inside the input box suffers from severe contrast and legibility degradation, appearing washed out, garbled, or unreadable against the underlying image content.

Steps to Reproduce

  1. In a thread, have an image (such as an image pasted in the conversation or generated by an agent) scrolled down towards the bottom of the chat view.
  2. Allow the image to scroll underneath the docked composer / prompt overlay.
  3. Type text or observe placeholder / prompt text in the input box over the translucent glass backdrop.
  4. Observe that the text rendering contrasts poorly or becomes difficult to read/distorted over high-contrast or textured image backgrounds.

Expected Behavior

Text in the composer input area should maintain strong legibility and clear contrast regardless of what is scrolled beneath the composer (e.g. through adequate opacity, contrast enforcement, or appropriate backdrop shielding).

Actual Behavior

Text rendered over the image area loses contrast and clarity, making glyphs difficult to distinguish and appearing washed out / partially obscured against image features.

Environment

  • T3 Code version: v0.0.43-nightly.20260923.2150
  • Platform: Desktop / Web app
  • OS: Ubuntu 24.04 LTS (Linux x86_64)

Screenshot

Text rendering over image bug

Additional Context

The composer uses a translucent backdrop layer (backdrop-filter: blur(12px) saturate(1.14) over ~80% surface background). When complex, high-contrast, or transparent/alpha image content scrolls beneath this glass layer, the text rendering layer above it suffers from legibility issues, particularly on Linux / Chromium environments.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs more infoInitial triage showed no bug. Awaiting more infovia-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions