Native <select> dropdowns never appear in streamed browser tabs#31502

opened15d agobyMMarcinusX

What happened

In a streamed browser tab, clicking a native <select> shows no dropdown, so a person viewing the stream can't see the options or pick one. Only the closed control is visible.

Seen in the macOS desktop app, viewing a browser tab hosted on another Mac through a linked environment.

Diagnosis

Streamed tabs have no <select> handling. File pickers do have a relay: the server catches filechooser (apps/server/src/preview/ServerBrowser.ts:534), sends it down the stream (ServerBrowserStream.ts:162), and the client renders a card (apps/web/src/browser/ServerBrowserSurface.tsx:825). The stream has no message for dropdowns. The only <select> support is the agent select action (ServerBrowserPage.ts:818), which sets the value without a popup.

In a direct test of T3's headless Chrome build, the dropdown opened (:open was true) but Page.startScreencast frames showed only the closed control. No CDP target appeared for the popup, so the file picker approach has no equivalent event to catch.

Possible fixes, both untested end to end:

  • Inject select, select::picker(select) { appearance: base-select; } so Chromium draws the popup in the page. In the test the open dropdown then showed in frames. Choosing an option and touch weren't tested, and it can change how sites look.
  • Relay options and position to the client, as with file pickers. This needs a new injected script, since streamed pages get none today.

Open question: a tab can render in headless Chrome or in the host desktop app's webview (ServerBrowser.ts:805). Only headless was tested, and it's unknown which one the reported tab used.

Steps to reproduce

  1. On Mac A, open the T3 Code desktop app with Mac B linked as an environment.
  2. In a thread on Mac B, open a browser tab on a page with <select><option>One</option><option>Two</option></select>.
  3. From Mac A, view the streamed tab and take control.
  4. Click the <select>.

Expected: the options appear and one can be chosen. Actual: no options appear.

Version

0.1.8-nightly.20261105.4205 on both the viewing and the hosting Mac.

Environment

Viewer: T3 Code Desktop on a MacBook Pro, macOS arm64 (Darwin 27.2.0). Host: Mac mini, macOS arm64, linked environment.

Evidence

shell
1Direct CDP test against T3's headless Chrome build, launch flags and viewport settings, not through the full T3 UI:
2
3| Dropdown | Open? | In screencast? |
4|---|---|---|
5| Regular `<select>` | Yes | No, closed control only |
6| `<select>` with `appearance: base-select` | Yes | Yes |
7
8- Clicking where an option should be changed nothing.
9- ArrowDown then Enter didn't change the value.
10- `color` and `date` inputs also showed no popup in frames, so they probably need a fix too. Typing digits into a date field worked.
11
12The symptom in the real UI is from the user's report. Source was read at v0.1.8-nightly.20261105.4205; the 9 commits on `main` since then add no `<select>` handling in the server browser files.
  • #25271 Streamed browser tabs are invisible to screen readers. Open PR #25308 adds an accessible view with form controls, which might work around this.
  • No existing issue found for <select> in streamed tabs.

Fix applied or workaround

No fix applied. Workarounds:

  • Use Open in system browser, though login state may not carry over.
  • Ask an agent to set the value with preview_act select.

Filed by

Claude Code (Claude Opus 5.5), via T3 Code triage.

Synced from GitHub

I can confirm this also affects the desktop webview. I first saw it while using a Mac to control a browser tab hosted by T3 Code 0.1.9 on Arch Linux. Clicking a native <select> focused the field on the Mac, but the options were visible only on the Linux host.

The attached 12-second recording is a separate, isolated reproduction using the Electron runtime bundled with that release (44.10.1). The left side shows the Linux desktop; the right side shows the guest’s live Page.startScreencast feed.

With the webview in the foreground, the menu opens directly below the field on the host, but the stream still shows a closed field. With the webview parked behind the host UI, the menu opens over that UI and is still absent from the stream. So correcting the host-side popup position alone would still leave remote users unable to see the options.

https://github.com/user-attachments/assets/31f6274e-892e-47c9-9cb6-7b5b46307d2e