Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Computer Use (Windows/UIA): snapshot element list is flattened in reverse pre-order; ToggleState not exposed

未關閉
  • 哪裡不對？
#67 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
49/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
python
領域
desktop

研究方向

Start by tracing the Windows computer-use snapshot code that builds the flat element listing and renders element attributes; the issue does not name those files or tests. Check how traversal order is produced and which UIA properties are included. Done means the listing follows forward pre-order (or documents its order) and exposes applicable state attributes, including ToggleState; run the relevant snapshot tests.

由索引模型根據 Issue 內容生成。

描述

Environment
  • ZCode computer-use plugin 0.6.3 (official), Windows 10 x64 (19045)
  • App under test: a GPUI (gpui-kit 0.7.0) Todo list on Windows, observed via the
    UIA accessibility path (get_app_state / getAXState)
Summary

Two consumer-side issues in the Windows computer-use snapshot element listing:

  1. Element order is reverse pre-order. The flat element list enumerates the
    UIA tree like a stack-based DFS that emits a node before pushing its
    children in order — equivalent to a DFS pre-order with every sibling group
    reversed. Flat indices therefore do not match visual order: within each
    container the list runs bottom-row → top-row. We verified this across four
    distinct container levels in one app (table rows, a toolbar, a form row, an
    inline edit card).

  2. ToggleState is missing from the listing. Checkbox elements show only
    checkbox (pressable) actions=[AXToggle,AXPress] with no state field, even
    though the element advertises the toggle action — which in UIA implies the
    Toggle pattern is registered and UIA_ToggleToggleStatePropertyId is
    readable. (By contrast, textfield value is shown, so attribute display
    is selective rather than absent.)

Why we're confident it's the snapshot layer, not the app toolkit

We verified the app's whole a11y chain is strictly order-preserving and
state-reporting:

  • gpui builds accesskit children in document order during prepaint DFS
    (window/a11y.rs:429-440, element.rs:367-406); NodeId is identity-only.
  • accesskit 0.24.1 Node.children is an ordered Vec; accesskit_consumer 0.38.0
    iterates it unchanged; accesskit_windows 0.34.0 Navigate uses
    filtered_children order (the filter drops, never reorders).
  • accesskit_windows registers TogglePattern with a proper ToggleState for
    checkboxes (node.rs:575-585, 1332-1335).
  • Windows Inspect.exe shows the same tree in visual order with readable
    ToggleState.

Replaying 12 captured snapshots against the reverse-pre-order model reproduced
the emitted listing character-for-character, including which elements
appear before/after others in every container. Tree-shape changes (adding a
row, opening an edit card) explain all frame-to-frame index shifts.

Impact

An agent clicking by flat index hits a visually different row than intended
(observed: "click row 2 by index" landed on visual row 3 — the click used the
element's own bounds, so it struck the element the index actually named).
Checkbox verification cannot be asserted from the snapshot at all.

Suggested fixes
  • Flatten in forward pre-order (FirstChild → NextSibling semantics), or at
    minimum document that flat order is reverse pre-order.
  • Include state attributes in element lines: ToggleState (On/Off), Value,
    IsSelected where applicable.
主要語言
Python
星號
124
分支
93
30 天內沒有已合併 PR

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

zai-org/zcode-plugins 的其他 Issue

查看 zai-org/zcode-plugins 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。