Support for shadow dom

[Kyle-Ignis]

Use case

the only alternative solutions for me are using a different testing framework for web that does support the shadow dom, I did some work on hacking the solution in myself on my own fork.

Proposal

Support on web for shadow dom

Anything else?

Hey! I am a QA engineer and have been playing with maestro and loving it. It's looking like a great cross platform solution for our mobile apps. I'm interested in using on our web platforms as well but running into issues because we use an open shadow dom on web. I played around a bit with hacking shadow dom support myself and got ~50% of the way there.

[linear]

MA-3021 Support for shadow dom

[brianpmaher]

Any update on this? We use Maestro for all of our platforms except web, because web makes heavy usage of shadow DOM. We don't need to support closed shadow DOM, just open shadow DOM. This is supported by other testing tools like Vitest, but would be slick to use a single testing framework across our stack.

[sklink]

Our workaround has been to use defined point clicks and delays against the shadow DOM component but it's not the most reliable solution.

We're otherwise blocked because shadow DOM is a requirement for our onboarding and successful onboarding is our primary use case for E2E.

@Kyle-Ignis I saw your draft PR here: #2289. Did you have any luck with your changes?