[🐛 Bug]: Standalone-Firefox: Bidi not active? about docker-selenium HOT 6 CLOSED

@AB-xdev, thank you for creating this issue. We will troubleshoot it as soon as we can.

from docker-selenium.

While starting the container, did you set this env var SE_NODE_ENABLE_CDP is true?
For bidi breakage changes, can you see https://www.selenium.dev/blog/2024/bidi-java-breaking-change/

from docker-selenium.

Thank you for the quick response.

While starting the container, did you set this env var SE_NODE_ENABLE_CDP is true?

As seen above in the docker inspect this variable is not set by me.

For bidi breakage changes, can you see https://www.selenium.dev/blog/2024/bidi-java-breaking-change/

We are already using the new imports inside the Java code that controls the test/containers (otherwise it won't compile) so it's likely a problem directly inside the container (where we didn't change anything).

from docker-selenium.

How are you creating the session? What capabilities are you sending? Are you setting webSocketUrl: true?

from docker-selenium.

How are you creating the session? What capabilities are you sending? Are you setting webSocketUrl: true?

Uhm no I didn't.
Set it to true, now it works :)
Thank you ^^

Is this documented somewhere? After specially searching for it I only found this in the MDN docs: https://developer.mozilla.org/en-US/docs/Web/WebDriver/Capabilities/webSocketUrl

from docker-selenium.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from docker-selenium.