accesskit_unix exposes the AT-SPI Text interface, but not EditableText. AT-SPI clients can read and focus text inputs, but they cannot replace the contents through the standard editable-text API.
Would it make sense to start with EditableText.SetTextContents and forward it as an ActionRequest using Action::SetValue and ActionData::Value? Methods without matching AccessKit actions could remain unsupported.
PR #362 intentionally left this interface out because Orca did not use it and Chromium did not implement it. It is useful for desktop automation clients, though. I ran into this with computer-use-mcp against egui and Bevy applications on Wayland: numeric controls expose AT-SPI Value, while text inputs have no equivalent string-setting capability.
I am happy to prototype the minimal mapping.
accesskit_unixexposes the AT-SPITextinterface, but notEditableText. AT-SPI clients can read and focus text inputs, but they cannot replace the contents through the standard editable-text API.Would it make sense to start with
EditableText.SetTextContentsand forward it as anActionRequestusingAction::SetValueandActionData::Value? Methods without matching AccessKit actions could remain unsupported.PR #362 intentionally left this interface out because Orca did not use it and Chromium did not implement it. It is useful for desktop automation clients, though. I ran into this with
computer-use-mcpagainst egui and Bevy applications on Wayland: numeric controls expose AT-SPIValue, while text inputs have no equivalent string-setting capability.I am happy to prototype the minimal mapping.