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

Use Webdriver client to replace geckodriver wrapper and webdriver classic methods #30301

Open
AtofStryker opened this issue Sep 26, 2024 · 0 comments · May be fixed by #30324
Open

Use Webdriver client to replace geckodriver wrapper and webdriver classic methods #30301

AtofStryker opened this issue Sep 26, 2024 · 0 comments · May be fixed by #30324

Comments

@AtofStryker
Copy link
Contributor

What would you like?

I would like to use the webdriver client, if possible, to handle webdriver classic and future BiDi automation methods, as well as start geckodriver for firefox using the wdiogeckodriveroptions capabilities

Why is this needed?

if we can correctly leverage the webdriver API to start geckodriver and drive webdriver methods, classic or bidi, it would allow us to delete the webdriver-classic and geckodriver wrapper introduced in #30250 (as we know how to patch geckodriver and what it needs to run correctly), further allowing us to lessen our code footprint (source and tests)

Other

No response

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