Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiremote: fluent async API and browser.asControl does not work #500

Open
Siolto opened this issue Jul 4, 2023 · 16 comments
Open

Multiremote: fluent async API and browser.asControl does not work #500

Siolto opened this issue Jul 4, 2023 · 16 comments
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@Siolto
Copy link
Collaborator

Siolto commented Jul 4, 2023

When using the multiremote feature of wdio the method chaining like:

await browser.one.asControl({
  selector: {...}
}).press()

does not work. The control is retrieved correctly from browser.one but wdio tries to press the control in both browsers.

When using the multiremote feature interacting with the same control over multiple browser at once via await browser.asControl()... does not work properly.

@Siolto Siolto self-assigned this Jul 4, 2023
@vobu vobu assigned vobu and unassigned Siolto Jul 14, 2023
@vobu vobu added the bug Something isn't working label Jul 14, 2023
@github-actions
Copy link

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

@github-actions github-actions bot added the stale label Aug 14, 2023
@github-actions
Copy link

closed 📴 because silencio 🤫 since an additional 14 days after staleness 📠

@vobu vobu reopened this Aug 28, 2023
@vobu
Copy link
Contributor

vobu commented Aug 28, 2023

this is still a shortcoming...

@vobu vobu removed the stale label Aug 28, 2023
@github-actions
Copy link

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

@github-actions github-actions bot added the stale label Sep 28, 2023
@vobu vobu removed the stale label Sep 28, 2023
@github-actions
Copy link

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

@github-actions github-actions bot added the stale label Oct 29, 2023
Copy link

closed 📴 because silencio 🤫 since an additional 14 days after staleness 📠

@vobu
Copy link
Contributor

vobu commented Nov 13, 2023

nooo, unfortunately not

@vobu vobu reopened this Nov 13, 2023
@github-actions github-actions bot removed the stale label Nov 14, 2023
Copy link

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

@github-actions github-actions bot added the stale label Dec 14, 2023
@vobu vobu removed the stale label Dec 14, 2023
Copy link

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

@github-actions github-actions bot added the stale label Jan 14, 2024
@vobu vobu removed the stale label Jan 15, 2024
Copy link

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

@github-actions github-actions bot added the stale label Feb 15, 2024
@vobu vobu removed the stale label Feb 15, 2024
Copy link

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

@github-actions github-actions bot added the stale label Mar 17, 2024
Copy link

closed 📴 because silencio 🤫 since an additional 14 days after staleness 📠

@vobu
Copy link
Contributor

vobu commented Apr 4, 2024

wrongfully closed - still a thing

@vobu vobu reopened this Apr 4, 2024
@vobu vobu removed the stale label Apr 4, 2024
Copy link

github-actions bot commented May 5, 2024

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

@github-actions github-actions bot added the stale label May 5, 2024
Copy link

closed 📴 because silencio 🤫 since an additional 14 days after staleness 📠

@vobu vobu added help wanted Extra attention is needed and removed stale labels May 21, 2024
@vobu
Copy link
Contributor

vobu commented May 21, 2024

this is still relevant

@vobu vobu reopened this May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants