Repository navigation
Replies: 1 comment
|
Same on desktop (macOS, nightly, dark theme). An agent opened a sign-in page in the floating preview and I could not find a way to close it. The dot sits on top of the website, so on a light page it looks like part of the page, not a T3 control. The toolbar only appears while the pointer is on that 12 px dot, so hovering anywhere else on the preview shows nothing. +1 for direction 2: a visible close or controls icon in place of the dot. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
On Android Chrome, I initially thought there was no way to dismiss the floating screen that shows the agent using the browser. I had no idea the small corner dot was tappable or that it revealed the toolbar and close button.
The documented phone workflow already supports this. This is a discoverability and accessibility concern: the low-contrast dot does not look like a control, and touch users have no hover cue to reveal what it does.
Two possible directions
The goal is for a mobile user to discover how to reveal the existing controls, including closing the floating preview, without needing to read the documentation first.
Scope and request for direction
I am proposing a small change to the affordance for the existing floating-preview toolbar, keeping its current actions and dismissal behavior. I searched related discussions; #6956 concerns the device toolbar inside preview chrome, and #16584 concerns opening the preview page in a system browser, rather than discovering this corner control.
Following the contribution guide, I would like maintainer approval of the direction and scope before implementing or opening a PR. Would improving this mobile affordance be welcome? Which of the two directions fits the intended design better, and are there constraints you would want a contribution to follow?
Prepared with Codex (gpt-6.1-sol) through T3 Code.
All reactions