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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[馃殌 Feature]: More details on bidirectional #1008

Open
alaahong opened this issue May 1, 2022 · 0 comments
Open

[馃殌 Feature]: More details on bidirectional #1008

alaahong opened this issue May 1, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@alaahong
Copy link
Member

alaahong commented May 1, 2022

Feature and motivation

Two kinds of proposals here.

  1. How to figure out the difference between BiDi and CDP ?
    As Firefox involved recently, it should be not in BiDi page if we have to import CDP with specific Chrome version, so any clear list to present what's the pure BiDi implement or specific Browser Vendor implementation?
    e.g. When I try to work on below sample with Selenium 4.1.4
    https://www.selenium.dev/zh-cn/documentation/webdriver/bidirectional/bidi_api/#listen-to-consolelog-events
    Seems all relative classes are from Chrome part, but it's in BiDi not the CDP page
    image

  2. As we known, the BiDi is working with WebSocket, but how to native work with BiDi?
    E.g. For WebDriver, I can request specific command via HTTP directly, but I have no idea how to work with BiDi via WebScoket directly?
    Try to review the BiDi W3C spec, seems that's a draft with many descriptions only. But I can't find out any guide or steps to call BiDi directly besides set webSocketUrl as true.

@diemol diemol added bug Something isn't working and removed needs-triaging labels Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants