[Bug]: Cant drag top bar of window (at least on 'what should we work on page') #13711

Activity

1. variousred

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Sep 25, 2026
2. variousred commented on Sep 25, 2026

   

   variousred

   on Sep 25, 2026

   Author

   More actions

   what a drag
3. juliusmarminge commented on Sep 25, 2026

   

   juliusmarminge

   on Sep 25, 2026

   Member

   More actions

   Confirmed on desktop 0.0.42 and on current main (ed809f7). Updating will not change this. The empty-project screen is the only workspace page that never installs a window drag region in the main pane.

   The red strip in your screenshot is the top of NoProjectsHero ("What should we work on?"). That view is a full-height SidebarInset with the empty state filling it, and it has no drag-region:

   https://github.com/pingdotgg/t3code/blob/ed809f7ad274ebccdfbf029ccfd7ff2582fd486a/apps/web/src/components/NoProjectsHero.tsx

   On Windows and Linux the desktop window uses a hidden title bar plus titleBarOverlay, so the window only moves where CSS sets -webkit-app-region: drag. The sidebar header is the only such region on this screen (SidebarChromeHeader). The wordmark inside it is a link, and links and buttons inside a drag region are explicitly no-drag, which is why only the padding at the very top left still moves the window. Collapsing the sidebar (collapsible="offcanvas") slides that header off-screen and leaves no drag surface at all.

   Every other workspace header already opts in through WorkspacePageHeader, which adds drag-region when running in Electron. That includes the no-active-thread empty state and the hosted "connect a computer" empty state. This page should use that same header.

   #6030 already describes this and adds an Electron-only titlebar spacer, but it still patches the old inline hero in _chat.index.tsx. That hero now lives in NoProjectsHero.tsx, and the shared header is WorkspacePageHeader, so the pull request needs a rebase onto that instead of a second spacer component. The failed "Couldn't start a new thread" state in _chat.index.tsx has the same missing header, on a screen this report does not hit.

   Workaround until that lands: drag from the empty padding in the sidebar title row, to the left of the wordmark. Keep the sidebar open.

   ❤️React with ❤️2Reacted by Michael Mitchell and Otavio Salvador
4. juliusmarminge

   added

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   and removed

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Sep 25, 2026
5. variousred commented on Sep 25, 2026

   

   variousred

   on Sep 25, 2026

   Author

   More actions

   thats funny 6030 made crayon drawings just like mine
6. Yash-Singh1

   closed this as completedin #13713on Sep 26, 2026