Skip to content

DevTools: element slugs change when a keyed Reactor list row only moves, so wait-for --gone reports it gone #1357

Open

Description

Found while testing #1197 (Reactor support in DevTools) with a small app that mixes XAML and Reactor, under winapp run . --watch --devtools on. This isn't blocking that PR; filing it so we track it once it lands.

What happens
In a keyed Reactor list, I reversed the list order in code. The rows kept their state (same keys), but the old DevTools slug for a row now returns "stale: no longer rendered". winapp ui wait-for border-aa49fc73ce --gone printed found: false in 0.2 s while the row was on screen.

Why
Slugs encode where an element sits in the tree, so moving it changes its slug. key=… keeps working and is the stable way to name a Reactor row.

Options

  • Make slugs for keyed Reactor elements stable across moves (derive them from component + key).
  • At minimum, have --gone treat "stale slug" as unknown rather than gone, and document that scripts should use key=, the C# name, or <Component> for Reactor elements.

Related: finding f2 on #1197 (--gone trusting an answer that doesn't prove the element is gone).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdevtoolsWinUI DevTools: toolbar, inspector, and winapp devtools commandsui-automation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions