-
Notifications
You must be signed in to change notification settings - Fork 317
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
Add BiDi support #1411
Comments
@gdonati78 WebDriver BiDi is not an approved standard (like W3C WebDriver is), it's only a draft. Console log and mutation observation should be already available using CDP. I'm not even sure that Selenium client does not rely on CDP internally for BiDi functionality. |
If I understand it correctly, the Selenium client seems indeed to rely on the CDP for mutation observation, but the console log functionality we are interested into is using W3C compliant BiDi, see links above or directly https://www.selenium.dev/documentation/webdriver/bidirectional/ |
@gdonati78 spec is in too early stage in our opinion. So far as Selenoid is backwards compatible, we don't want to reimplement things (and thus break backwards compatibility) if one day Selenium guys decide to change things slightly. |
It makes sense, thanks for the prompt answer @vania-pooh |
For now, in Chrome, as I remember, BiDi is implemented using CDP internally. The goal of BiDi is to not rely on CDP at all in the future from Selenium side to have one common way of bidirectional communication. So even though CDP might be used, from Selenium we should already be able to use BiDi.
However, as @vania-pooh and @gdonati78 stated correctly, it is not accepted standard yet.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
In Selenium 4 there are constantly new features added that are based on the BiDirectional protocol. I'm specifically interested in e.g. the console log, but also the mutation observation
As far as I understand it also uses WebSocket like the existing CDP (something was added in #1063).
The text was updated successfully, but these errors were encountered: