feat(simulation): expose and record real mouse input - #47194
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Simulation can click an element, but cannot move a pointer through real hover/leave states or hold a button while dragging. Recorded terminal output also contains no mouse coordinates, so Drive cannot show viewers where those interactions happened.
What Changes
Add optional
ui.mouseandui.recording.pointercapabilities without changing existing click behavior or the terminal-v1 recording format.*.pointers.jsonlsidecar timestamps input on the same monotonic clock as terminal output. Older terminal recording readers remain compatible.Demo
spring-smooth.mp4
Real production TUI controlled by Drive: native action hover and leave, target-relative click, down/up theme toggles, and resize. The pointer is composited during export by the companion Drive change; interpolation sends no additional input. Captured with this implementation before its clean rebase (
52974a6057), rendered with Drive961e75b; no model requests or playback acceleration. This PR adds simulation capabilities, not a production TUI layout change.Scope
Canonical simulation protocol, real renderer input dispatch, and portable mouse recording evidence. Cursor styling and spring interpolation remain Drive-owned. Existing operations continue to work with clients that do not request the new capabilities.
Verification