Skip to content

[Bug]: "No project" label is shortened to "No …ect" on the new-thread screen #21347

Closed

Description

@vwgp8wkgjz-beep

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 the new-thread screen.
  2. Start a thread without a project (the "or start without a project" link, or the New thread without project shortcut).
  3. Look at the project picker under "What should we work on?".

Expected behavior

The picker reads "No project" in full. It is a short label and there is plenty of room for it.

Actual behavior

The picker reads "No …ect", whatever the window width.

From reading the code, I think two changes merged on 2026-10-18 combine to cause this:

A possible fix is to apply the 1em cap only when the picker sits inside the headline next to the "?". I haven't tested that.

Impact

Cosmetic issue

Version or commit

Nightly build from 2026-10-18. The code above is unchanged on main @ 8cd9641

Environment

macOS, T3 Code (Nightly) desktop app

Screenshots, recordings, or supporting files

Image

Workaround

None needed. The picker still works; only its label is cut short.

Activity

  1. juliusmarminge commented on Oct 18, 2026

    @juliusmarminge
    Member

    Note

    Grok responding on behalf of Julius.

    Confirmed on current main. The project picker trigger in DraftHeroHeadline.tsx always carries the max-w-[calc(100%-1em)] cap from #17208, which exists to leave room for the trailing "?" in the headline. For no-project drafts the same picker renders alone in the subtitle <p> with no "?" after it, and that <p> sits in an items-center column, so it is only as wide as its content. The cap then comes out about 1em short of the label, and DraftProjectName from #18858 middle-truncates to that width, giving "No …ect".

    Marking this as an accepted cosmetic bug. Thanks for the precise diagnosis.

  2. added
    acceptedfeature request accepted
    bugSomething is broken or behaving incorrectly.
    via-triageFiled through npx t3 triage
    on Oct 18, 2026
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

    acceptedfeature request acceptedbugSomething is broken or behaving incorrectly.via-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