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

[PROTOTYPE] RFC-212 Enable testdriver BiDi on-demand in Chrome #48618

Draft
wants to merge 1 commit into
base: sadym/require-bidi
Choose a base branch
from

Conversation

sadym-chromium
Copy link
Contributor

@sadym-chromium sadym-chromium commented Oct 15, 2024

This prototype is not intended to be merged

Prototype of using RFC 212 in Chrome implementation.

Choose chome transport based on require_webdriver_bidi setting introduced in #48622

@sadym-chromium sadym-chromium force-pushed the sadym/bidi-on-demand branch 2 times, most recently from 209f045 to b5ceae5 Compare October 21, 2024 12:46
@sadym-chromium sadym-chromium changed the base branch from master to sadym/require-bidi November 7, 2024 12:59
@sadym-chromium sadym-chromium changed the title [DRAFT] Enable testdriver BiDi on-demand [PROTO] Enable testdriver BiDi on-demand Nov 7, 2024
@sadym-chromium sadym-chromium changed the title [PROTO] Enable testdriver BiDi on-demand [PROTOTYPE] RFC-214 Enable testdriver BiDi on-demand in Chrome Nov 14, 2024
@sadym-chromium sadym-chromium changed the title [PROTOTYPE] RFC-214 Enable testdriver BiDi on-demand in Chrome [PROTOTYPE] RFC-212 Enable testdriver BiDi on-demand in Chrome Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants