[Bug]: Custom viewport size input focus ring is clipped on macOS
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start in apps/desktop with the in-app browser's custom viewport sizing controls and reproduce the focused width or height field on macOS. Inspect the control's layout and focus styling around the 1920 × 1080 fields. Done means the outer focus ring is fully visible on all edges while custom sizing still works.
Written by the indexing model from the issue text.
Description
Before submitting
- I searched existing issues and did not find a matching report.
- I included the available details needed to investigate the visual defect.
Area
apps/desktop — in-app browser custom viewport sizing controls.
Steps to reproduce
- Open the in-app browser in the T3 Code macOS desktop app.
- Switch to custom viewport sizing.
- Focus one of the width or height fields (the supplied crop shows the height field with
1920 × 1080entered). - Look at the lighter purple outer focus ring.
These steps are based on the reporter's screenshot and description; I did not independently replay them.
Expected behavior
The outer focus ring is fully visible around the focused size field, including its top and bottom edges.
Actual behavior
The lighter purple outer ring around the focused 1080 field is cut off at both the top and bottom. The inner purple border remains visible. The crop also shows the bottom of the control meeting the toolbar's horizontal divider, consistent with vertical clipping in that row.
Impact
Cosmetic issue. The screenshot establishes clipped focus styling; it does not show a failure to enter or apply a custom size.
Version or commit
The locally installed T3 Code (Nightly) app reports 0.0.43-nightly.20260925.2237. The exact build used when the screenshot was captured has not been independently confirmed.
Environment
macOS 27.2, T3 Code desktop app, in-app browser custom viewport size controls. The supplied screenshot is a cropped 316 × 104 PNG at 2× scale. Appearance and display scaling beyond the image's 2× capture are not confirmed.
Screenshots, recordings, or supporting files
The reporter supplied a cropped screenshot in the originating T3 Code thread, captured on 2026-09-25 at 11:30. It shows the 1920 × 1080 controls and the clipped lighter purple ring around 1080. The screenshot could not be transferred to GitHub through the available issue connector.
Workaround
None established.
- Dominant language
- TypeScript
- Stars
- 23.6k
- Forks
- 6.1k
- Avg merge
- 8h 51m
- Merged PRs (30d)
- 350
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pingdotgg/t3code#14067 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pingdotgg/t3code#14066 · 1 comment ·
Maintainers usually reply within 1 day
-
bug upstream via-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
pingdotgg/t3code#13990 · 1 comment ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
pingdotgg/t3code#13977 · 1 comment ·
Maintainers usually reply within 1 day
-
needs more info via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
pingdotgg/t3code#13851 · 3 comments ·
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#611 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
polka-codes/test#345 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
GoogleChromeLabs/project-sesame#217 ·
Maintainers usually reply within 12 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
solana-foundation/solana-com#2202 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100