Closed mario-s closed 2 years ago
Update to this topic:
When I remove the Xpra container and launch a standalone Selenium 4.1.2 server on my machine, it neither works with Selenium 4 and the Proxy. Here are my setups and the outcomes.
The response from the proxy during a lookup for an element is different to the one from the server itself. Proxy:
{
"value": {
"ELEMENT": "4264a7dc-e356-49f4-b7d4-ae40986ad9a8"
}
}
Selenium Standalone Server:
{
"value": {
"element-6066-11e4-a52e-4f735466cecf": "4264a7dc-e356-49f4-b7d4-ae40986ad9a8"
}
}
facing the same problem
Fixed in healenium/hlm-proxy:0.2.5
Hi,
im trying to run a setup with with selenium xpra and Selenium 4.0.0/4.1.0. The browser starts and I'm able to navigate to a webpage and find an element. However the elemnt is not of type
selenium.webdriver.remote.webelement.WebElement
it is of typedict
. So that means I can not interact with it via aclick()
action. Is the docker infrastructure not compatible with Selenium 4.x.x?I'm using Python 3.8.5 with this is docker-compose file:
When I execute this python script, I get a dictionary, not the WebElement, as expected.