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.

Sign up for GitHub

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

Jump to bottom

automation: Consider adding WebDriver BiDi actions in addition to the WebDriver Classic endpoints #288

Open
rakuco opened this issue Jun 20, 2024 · 0 comments
Open

automation: Consider adding WebDriver BiDi actions in addition to the WebDriver Classic endpoints #288

rakuco opened this issue Jun 20, 2024 · 0 comments
Labels
enhancement New feature or request V2

Comments

@rakuco
Copy link
Member

rakuco commented Jun 20, 2024

As discussed in #284 (comment):

defining it [the API] as a WebDriver BiDi module would allow adding events later (if needed) and it would allow WebDriver BiDi-only clients such as Puppeteer to expose the functionality for developers to write tests for their apps.

We do not need BiDi's bidirectional capabilities at the moment, but I don't think it would hurt to define a BiDi module in the future, just like the Permissions API does.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request V2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rakuco @arskama