Drive v2.0.1 exposes ui.click, but no pointer-motion operation. While reproducing an OpenCode composer selection bug, I need to park the pointer while a panel is closed, open it with the keyboard, then move within a row without activating it.
Please expose a ui.move or ui.mouse.move operation that sends a real mouse-motion event through the TUI input path. This would make hover-versus-keyboard regressions reproducible without using a click just to position the pointer or relying on raw escape sequences.
OpenCode revision under test: 97303c39dd153b64d7036249b279490201820b19. The OpenCode bug is separate: layout-generated hover currently changes the composer selection.
Drive v2.0.1 exposes
ui.click, but no pointer-motion operation. While reproducing an OpenCode composer selection bug, I need to park the pointer while a panel is closed, open it with the keyboard, then move within a row without activating it.Please expose a
ui.moveorui.mouse.moveoperation that sends a real mouse-motion event through the TUI input path. This would make hover-versus-keyboard regressions reproducible without using a click just to position the pointer or relying on raw escape sequences.OpenCode revision under test:
97303c39dd153b64d7036249b279490201820b19. The OpenCode bug is separate: layout-generated hover currently changes the composer selection.