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
The example config.toml file in the readme for the dynamic grid setup configures the edge containers as msedge instead of the new name MicrosoftEdge. If one uses EdgeOptions() from selenium 4, one cannot directly connect to these containers (one can change browserName as a workaround`).
To Reproduce
Start the docker-compose-v3-dynamic-grid.yml using the config.toml from the readme.
Start a script using selenium 4 and EdgeOptions
Capability cannot be fulfilled
Expected behavior
Edge Container should successfully start/names in this repository and other selenium repositories should be consistent.
Changing {\"browserName\": \"msedge\"}" to {\"browserName\": \"MicrosoftEdge\"}" in config.toml fixes the problem.
🐛 Bug Report
The example
config.toml
file in the readme for the dynamic grid setup configures the edge containers asmsedge
instead of the new nameMicrosoftEdge
. If one usesEdgeOptions()
from selenium 4, one cannot directly connect to these containers (one can changebrowserName
as a workaround`).To Reproduce
docker-compose-v3-dynamic-grid.yml
using theconfig.toml
from the readme.Expected behavior
Edge Container should successfully start/names in this repository and other selenium repositories should be consistent.
Changing
{\"browserName\": \"msedge\"}"
to{\"browserName\": \"MicrosoftEdge\"}"
inconfig.toml
fixes the problem.Test script reproducing this issue
Environment
OS: Linux
Docker-Selenium image version: 4.0.0-beta-3
Python-selenium version: 4.0.0b3
The text was updated successfully, but these errors were encountered: