can't or stuck when find the element using the css selector

[fikri-r-scp]

Is there an existing issue for this?

• I have searched the existing issues and didn't find mine.

Steps to reproduce

1. my code:

url: "https://mytestingsite.com"
---
- launchApp
- runFlow: ../../../elements/loadElements.yaml
- runFlow: ../../../subflows/login.yaml
- tapOn:
    css: "button[aria-label='Open user menu']"

The HTML contains this;

<button class="rounded-full ring-2 ring-transparent hover:ring-blue-400 focus:ring-blue-500 focus:outline-none transition-all duration-200 cursor-pointer" aria-label="Open user menu" type="button" id="radix-:r56:" aria-haspopup="menu" aria-expanded="false" data-state="closed"><span class="after:content-[''] after:block after:absolute after:inset-0 after:rounded-full after:pointer-events-none after:border after:border-black/10 dark:after:border-white/10 relative flex shrink-0 overflow-hidden rounded-full w-10 h-10"><span class="flex h-full w-full items-center justify-center rounded-full bg-primary text-primary-foreground text-xs">FR</span></span></button>

2. Run the flow with maestro test flowtest.yaml

Actual results

The maestro is stuck in the tapOn step (step 2)

Note

• if i use childOf in

- tapOn:
    css: "button[aria-label='Open user menu']"
    childOf:
      id: "mytestId"

it said: Element not found error

Expected results

should correctly detect the CSS

About app

Web

About environment

WEB
Windows 11
Maestro CLI 2.5.0

Logs

No response

Maestro version

2.5.0

How did you install Maestro?

install script (https://get.maestro.mobile.dev)

Anything else?

No response

[linear]

MAE-468

[Fishbowler]

And what happens without the childOf selector?

[fikri-r-scp]

And what happens without the childOf selector?

it just stuck on tapOn step, (i wait for about 5 minutes or more

[Fishbowler]

So we should remove all the childOf stuff so that it's not muddying the issue?

If I take that HTML and pop it in a page, will the tapOn with just the CSS reproduce the problem?

[fikri-r-scp]

So we should remove all the childOf stuff so that it's not muddying the issue?

If I take that HTML and pop it in a page, will the tapOn with just the CSS reproduce the problem?

yes, it should be reproducible when you use the HTML