Open l1444 opened 3 years ago
I'm seeing that the selenium-rs
is not communicating well with the the local Selenium API. It's returning sessionId: null
to selenium-rs
when trying to find an element, which selenium-rs
requires in the response (ElementResponse
). I have a fix incoming, but it's relatively large and changes some semantics.
As an aside: does anyone have a reference to the standalone Selenium server REST API (for selenium-server-standalone-3.141.59.jar
)? It would be incredibly useful for this fix. I seem to be unable to find it in ~10m of web searching.
Here's a hacky workaround I whipped up (sorry for the whitespace changes). I only updated find_elements
but the same hack can be applied to other functions I'm sure.
As an aside: does anyone have a reference to the standalone Selenium server REST API [...]?
I'm struggling without this too! The fundamental issue I don't really understand is why the sessionId
field is null
, or why an element needs it's own session id at all. But I'm not really that knowledgeable of Selenium, I just use it occasionally.
hello, I'm using the code that is provided in the documentation so this one:
and it shows me this error: