Repository navigation
Description
Is your feature request related to a problem? Please describe.
Following #798: with 0.7.1 we moved every pointer and keyboard press in our WinUI 3 UI suite (49 suites, PowerShell 7) onto winapp ui. A suite finds the element in-process with UI Automation and hands it to winapp to press. Scoped and typed queries, FontWeight through get-property, --action toggle-on and the DPI in status all work as described against our app. Thank you for those.
Six gaps decide where we still keep input of our own or work around winapp. Each is small, and they came out of the same port, so they are listed together.
- The press verbs take no
--root/--type, and a text selector is a substring.search,get-propertyandwait-fortake--root,--typeand--class-name;click,hover,invoke,drag,scrollandset-valuedo not, and their selector matches any name that contains it.winapp ui click "Allodia Mail & Calendar" -w <hwnd>pressed a list row named "Welcome to Allodia Mail & Calendar" rather than the title-bar text named exactly that. We now resolve a slug withsearch … --type, match name and bounds ourselves, and only then press, which costs a secondwinappprocess per press. --class-namecannot be the whole query.searchrequires a text selector, so--class-namenarrows a text match but cannot stand alone. "The element of classCalendarSurface" cannot be asked without knowing its name, and*matches nothing.clickandhovertake no point.touch --at x,yanddrag x,y x,yaccept coordinates;clickandhoveraccept only a selector. Some presses need a point: inside a WebView2's page, or on part of a control rather than its centre (the header line of an expanded tree row, whose bounds take in its children). We currently right-click a point withdrag <p> <p> --right, which works but reads as something else.- No horizontal wheel.
scroll --wheel Nsynthesises vertical notches only. Our calendar pans on a horizontal wheel (a tilt wheel or a touchpad), so we still injectMOUSEEVENTF_HWHEELourselves. touch --gesture pinchhas no angle. Pinch and stretch spread along one axis. A diagonal pinch is the only way to exercise a two-axis zoom, which we inject with our ownInjectTouchInputhelper.invokableAncestoringet-propertycarries empty geometry. For aTextBlockinside a list item, the nested object reads"isEnabled": false, "x": 0, "y": 0, "width": 0, "height": 0, while the same ancestor read on its own is enabled with real bounds. A consumer of the nested object gets a disabled element at the origin.
Our code base is open source and can be found here: https://github.com/allodia-eu/mail-calendar/tree/30c8523d2d3865c8a3a6662ff6ef0de165bb401c/clients/windows
Describe the solution you'd like
--root,--typeand--class-nameonclick,hover,invoke,drag,scrollandset-value, with the same meaning they have onsearch; and an exact-name option (--exact, orname=in the selector) on every verb that takes a selector.--class-name(and--type) accepted without a text selector.--at x,yonclickandhover, in the physical screen coordinatesinspectreports.- A horizontal wheel:
--wheel-horizontal N, or--wheel N --axis horizontal. --angle <degrees>fortouch --gesture pinchandstretch.invokableAncestorpopulated with the ancestor's realisEnabledand bounds, or those fields left out.
Additional context
Windows 11 Pro ARM64 10.0.26200, winapp 0.7.1, WinUI 3 (Windows App SDK 2.4.0) unpackaged Debug build, PowerShell 7. The cycle through a WebView2 that we hit during the same port is reported separately as a bug.
Activity
uiverbs that take a selector #1090--class-name/--typebe the wholeuiquery, with no text selector #1095--at x,yforui clickandui hover#1091ui scroll#1092--angleforui touch --gesture pinch/stretch#1093invokableAncestorinuiJSON reports a disabled element at 0,0 #1094nmetulev commentedon Oct 14, 2026
Thanks Dennis Ameling (@dennisameling). I split up the issue into sub issues to track individually
Add --at x,y to ui click and ui hover (#1103)
Prefer an element named exactly the selector text in single-element u…
Let --type and --class-name be the whole `winapp ui` query (#1104)
Add `--wheel-horizontal` to `winapp ui scroll` (#1100)
Fix ui --json reporting invokableAncestor as disabled at 0,0 (#1099)
Add --angle to ui touch pinch/stretch (#1098)