You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently selenium and Selenoid split off on how they wish to support cdp. This gem seems to have a good springboard for attaching to existing Selenoid chrome sessions over the devtools endpoint, and I've been trying to figure out what all changes would be necessary for this. I noticed that the gem itself will not stand up a process if it detects that there is an existing web socket and selenoid does expose a web socket endpoint per the following spec https://github.com/aerokube/selenoid/blob/master/docs/devtools.adoc
Proposal
Add a way to specify a websocket to attach to at spin up to bypass kickstarting a process.
Findings
So far i've attempted this and have found that passing the selenoid endpoint errors out as they do not support /json/version
I've stood up an issue with them asking if they would be willing to add support for it. aerokube/selenoid#1322
The text was updated successfully, but these errors were encountered:
Background:
Recently selenium and Selenoid split off on how they wish to support cdp. This gem seems to have a good springboard for attaching to existing Selenoid chrome sessions over the devtools endpoint, and I've been trying to figure out what all changes would be necessary for this. I noticed that the gem itself will not stand up a process if it detects that there is an existing web socket and selenoid does expose a web socket endpoint per the following spec https://github.com/aerokube/selenoid/blob/master/docs/devtools.adoc
Proposal
Add a way to specify a websocket to attach to at spin up to bypass kickstarting a process.
Findings
So far i've attempted this and have found that passing the selenoid endpoint errors out as they do not support
/json/version
I've stood up an issue with them asking if they would be willing to add support for it.
aerokube/selenoid#1322
The text was updated successfully, but these errors were encountered: