[Bug]: Terminal drawer toggle has no spacing from "Commit, push & PR" and its hover/tooltip overlaps it
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- electron, typescript
Research direction
Look in the desktop app's codebase under apps/desktop for the toolbar component, likely in a file like Toolbar.tsx or similar. Inspect the styling for the terminal drawer toggle button and compare its margin/padding with neighboring buttons like 'Commit, push & PR'. Check the hover/tooltip implementation to ensure it doesn't overflow. Running the app locally and inspecting the element with dev tools will help verify the fix.
Written by the indexing model from the issue text.
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
- Open the T3 Code desktop app (Linux) and open a project/thread.
- Look at the top toolbar:
Add action,Open,Commit, push & PR, then the terminal drawer toggle (tooltip "Toggle terminal drawer (Ctrl+J)"). - Hover the terminal drawer toggle.
Expected behavior
The terminal drawer toggle should have the same spacing/margin as the other toolbar controls, and its hover state/tooltip should stay inside its own bounds and not overlap the Commit, push & PR button.
Actual behavior
There is no margin between the terminal drawer toggle button and the Commit, push & PR button. When hovering, the hover state/tooltip is drawn on top of the Commit, push & PR button.
Impact
Cosmetic issue
Version or commit
0.0.43-nightly.20260924.2200 (x86_64 AppImage, build 473ee9c)
Environment
CachyOS (Arch-based), Linux kernel 7.2.6-1-cachyos, x86_64; T3 Code desktop app (Electron). Report filed via opencode using model opencode-go/deepseek-v4.1-flash.
Screenshots, recordings, or supporting files
- Dominant language
- TypeScript
- Stars
- 23.4k
- Forks
- 6k
- Avg merge
- 9h
- Merged PRs (30d)
- 349
Contributor 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
-
accepted bug good first issue via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
accepted bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
accepted bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
accepted bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug upstream via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
All issues in pingdotgg/t3code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100