Proto commits in slint-ui/slint

These 47 commits are when the Protocol Buffers files have changed:

2026-09-30

testing: match elements by accessible label in queries Add ElementQuery::match_accessible_label() and a matching match_element_accessible_label query instruction to the system testing protocol, and list it in the MCP tool descriptions. slint-testing 0.4 matches labels on the Python side: it fetches every candidate's properties with a separate request. Evaluating the match in the application makes a label query a single request. The Visual Editor UI tests look up most elements by label. ElementHandle::find_by_accessible_label() now uses the new match instead of its own predicate.

2026-09-26

Add native click targeting and automatic scrolling to Python tests Negotiate a read-only native left-click target contract and reveal clipped controls through nested Flickables. Check again after hover callbacks before pressing, preserve explicit unsupported policies, and keep older binaries on labeled basic readiness. Record target checks and scrolling in Studio actions. Validate against a standalone native fixture, the legacy Python runtime, and the editor. Keep the protobuf descriptor checked against the Rust schema and include it in Studio's preflight cache identity. Validation: 655 editor UI tests, 213 editor Rust tests, 77 backend tests, 59 generic Python tests, and 68 Studio tests passed. Native Studio reran four inspector cases and displayed their captures. Ruff, ty, repository autofixes, and strict backend/root-workspace Clippy passed. Full repository Clippy is blocked by the examples workspace's FFmpeg/header incompatibility. ChangeLog: Improve Python UI test clicks with native target checks and automatic scrolling.

2026-09-11

mcp: hold modifiers during move_pointer too hover_element and move_pointer both dispatch a PointerMoveEvent and differ only in target (element handle vs. raw position), same as the scroll_element/ dispatch_pointer_scroll pair, which already takes modifiers on both variants. move_pointer was the odd one out.

mcp: hold keyboard modifiers during a pointer gesture A shift-click was three calls: a key press of '\u{0010}', the click, then the release. Every embedder had to rediscover that Shift is that code, and a modifier-sensitive gesture couldn't be expressed as one call. The pointer tools now take a `modifiers` object. Slint reads the modifiers of a pointer event from the window's key state rather than from the event, so the keys are pressed before the gesture and released after it. A guard does the releasing on drop, so a gesture that fails in between doesn't leave the window with a key stuck down. `click_element` and `drag_element` carry the field into the systest transport as well, since both transports share the dispatch functions. ChangeLog: MCP pointer tools accept a `modifiers` object, so a shift-click or a ctrl+wheel zoom is one call.

2026-09-09

mcp: add wheel events to the tool surface A client could move, click and drag the pointer but never scroll it, so a Flickable or ScrollView couldn't be scrolled and a wheel-driven canvas zoom wasn't reachable at all. Working around it meant finding the application's own scroll or zoom controls in the element tree and clicking them repeatedly. `ElementHandle::scroll` already dispatches `PointerScrolled` at an element's center, so the two tools are thin: `scroll_element` takes a handle and `dispatch_pointer_scroll` an arbitrary point, mirroring the existing `hover_element` and `move_pointer` pair. ChangeLog: The MCP server has new `scroll_element` and `dispatch_pointer_scroll` tools, to send mouse wheel events.

2026-09-01

testing: Add hover_element and move_pointer tools to the MCP server `click_element` and `drag_element` both press a button, so there was no way to produce a plain hover: any attempt to move the pointer over an element also delivered a press to it. Hover states, tooltips and menu highlighting were therefore out of reach over MCP. `hover_element` moves the pointer to an element's center, reusing the same `absolute_center` that `click_element` targets so a hover lands where a click would. `move_pointer` moves it to a position in the window, which is what clearing a hover needs. Neither presses a button. They are two tools rather than one with alternative targeting fields so that each `inputSchema` states exactly which arguments are required, as every other tool with arguments already does. Both boil down to dispatching a PointerMoved window event, which the systest wire protocol can already do via RequestDispatchWindowEvent. So RequestMovePointer/RequestHoverElement are kept only as free-standing message shapes for the MCP tools' input schemas, not added to the RequestToAUT/AUTResponse oneofs, and systest.rs no longer special-cases them. ChangeLog: The MCP server has new `hover_element` and `move_pointer` tools, to hover an element or a position without pressing a button.

2026-08-29

Add a title-bar accessible role Maps to AccessKit's TitleBar and Qt's TitleBar role, so a custom title bar in a frameless window can expose the right semantics.

2026-08-28

Add a title-bar accessible role Maps to AccessKit's TitleBar and Qt's TitleBar role, so a custom title bar in a frameless window can expose the right semantics.

Move WindowEventDispatchResult to slint::platform The enum now sits next to WindowEvent, where backends look for it. Drop the Ignored variant. To a backend, an event that nothing handled and one that a handler refused mean the same thing, so Rejected covers both. The Node.js port follows: the enum moves into the platform namespace, and the docs sidebar now lists that namespace's enums. RecordedEventResult in the system testing protocol loses its Ignored value too, since nothing can produce it any more. cc #13066

2026-08-27

Add a title-bar accessible role Maps to AccessKit's TitleBar and Qt's TitleBar role, so a custom title bar in a frameless window can expose the right semantics.

2026-08-13

add missing accessibility properties ( item_count, item_index, ...) to the testing crate. (#12892) (cherry picked from commit 3f269063d5f53e3774301fe204716293cbf7e2b6)

add missing accessibility properties ( item_count, item_index, ...) to the testing crate. (#12892)

2026-07-06

system testing / MCP: Expose the window scale factor in the window properties (cherry picked from commit a7f9413f5a084dcd32d088910de516d7464eba75)

2026-07-02

system testing / MCP: Expose the window scale factor in the window properties

system testing / MCP: Expose the window scale factor in the window properties

2026-05-28

accessibility: Add landmark accessible roles (#11831) Add banner, complementary, content-info, form, main, navigation, region, and search roles to AccessibleRole with mappings for the AccessKit, Qt, and testing backends. Use navigation and main landmarks in the gallery demo.

2026-05-23

Add MCP event log for processed window events (#11665) - add an internal window-event dispatch hook and shared testing-backend event ring buffer - expose get_event_log and clear_event_log MCP tools, plus systest responses for the same log - record pointer/key/window events with sequence cursors, dropped counts, and key processing results - preserve extended pointer buttons and keep event-log pagination/clear cursors monotonic

2026-05-20

widgets: Add RadioGroup (#11141) * feat: add RadioGroup and docs/example updates

2026-04-14

Drive MCP tool definitions and dispatch from proto messages Replace hand-written JSON schemas and manual string parsing with proto-driven generation: - Add RequestGetElementTree, RequestDispatchKeyEvent, and KeyEventType to slint_systest.proto so all 12 MCP tools have proto counterparts - Generate JSON schemas from proto descriptors at build time in build.rs - Replace 160 lines of hand-written JSON with a declarative TOOLS table mapping tool names to proto request types - Unify all tool handlers to use deserialize_params with proto types, eliminating manual string matching for enums and field extraction

2026-04-13

Add drag gesture simulation to testing backend and MCP server Add drag() and mock_drag() methods to ElementHandle that simulate a pointer drag from the element's center to a target position. The pointer is pressed at center, moved in interpolated ~5px steps (below the 8px DISTANCE_THRESHOLD), then released at the target. Zero-distance drags short-circuit to a press-release without spurious move events. Expose the new capability through both transports: - systest: RequestElementDrag / ElementDragResponse proto messages - MCP: drag_element tool with targetX, targetY, optional button Also adds MCP server documentation to the testing backend README and two unit tests covering normal drags and zero-distance edge case.

2026-03-30

Rename FlexBoxLayout to FlexboxLayout and LayoutKind::FlexBox -> LayoutKind::FlexboxLayout for consistency with the other enum values in LayoutKind In internal/backends/testing/slint_systest.proto, move the comment about Unknown to the AccessibleRole where it initially belonged (commit 2cad49eb9b32c inserted enum LayoutKind between the comment and the AccessibleRole enum) Fixes #11152

2026-03-07

Address review: use LayoutKind enum, rename proto variants, add tests - Replace SharedString return with a proper LayoutKind enum in ElementHandle::layout_kind() - Rename proto enum variants to match element names (HorizontalLayout, VerticalLayout, GridLayout) - Add test covering all layout kinds and non-layout elements

Expose layout kind through the test protocol Encode the layout kind (h-box, v-box, grid, flex-box) as a third field in the debug info string emitted by the compiler, and surface it through ItemRc, ElementHandle, and the systest protobuf protocol. This allows test tooling to distinguish layout elements from plain rectangles.

2025-11-03

Add `AccessibleRole.radio-button`

2025-06-25

system-testing: Make the image format for snapshots configurable Let the image crate pick an encoder by mime-type, otherwise fall back to png. Renaming the field in the response is compatible, as only the tag numbers are encoded. Adding a field to the request is also compatible as every field is optional.

The documentation is generated from this commit.

2025-06-19

system testing: Expose accessible-enabled and accessible-read-only

2025-06-17

system testing: Expose accessible-placeholder-text in the element properties

2025-02-18

Add `AccessibleRole::Image` and use it in the `AboutSlint` widget (#7593) * Add `AccessibleRole::Image` * Improve accessibility of the `AboutSlint` widget * Filter out some images from the accessibility tree

2025-02-03

Add the `accessible-action-expand` action

2025-01-10

Rename AccessibleRole.GroupBox to AccessibleRole.Groupbox While unfortunate in casing, this is consistent with Checkbox, Combobox, and Spinbox.

Janitor: Remove trailing whitespaces from all files `git grep -I -l -O'sed -i "s/[[:space:]]*$//"' -e ''`

2025-01-07

Add `AccessibleRole::GroupBox`

2025-01-06

Add `AccessibleRole::TabPanel`

2024-09-19

ui-testing: Add support for reading the computed opacity of elements This is useful when the UI shows for example labels that appear and the screenshot for referenceing is meant to be taken when the opacity animation is complete and the value is (near) 1.0.

2024-09-16

Changelog: Introduce `AccessibleRole::ListItem`

2024-08-20

Add the window's root element handle to the window properties

System Testing: Add descendent and element id/type/role matching messages

2024-07-16

system testing: Add support for dispatching pointer and key window events

2024-07-05

API Review: Remove SharedImageBuffer from public API and rename Window::grab_window() to take_snapshot() Use SharedPixelBuffer as return value for take_snapshot() and provide counter-parts to from_rgb* in Image as to_rgb*

2024-06-28

Changed ElementHandle click API to a single_click and double_click function taking the button That way one can also simulate double right click, for example. This is a little less convenient, more generic, but a reasonable compromise (perhaps :-)

System Testing: Add support for clicking on elements

2024-06-27

System testing: Add support for grabbing window contents as PNG encoded image

2024-06-14

System Testing: Expose the accessibility role of elements

2024-06-13

Add support for setting the accessible value

Add a way to invoke accessibility actions

Testing: Add the ability to locate elements by id and expose various properties

Add plumbing for system testing