Skip to content

[Bug]: Custom viewport size input focus ring is clipped on macOS #13607

Description

@thxgg

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

  1. Open the in-app browser in the T3 Code macOS desktop app.
  2. Switch to custom viewport sizing.
  3. Focus one of the width or height fields (the supplied crop shows the height field with 1920 × 1080 entered).
  4. 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.

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

    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