Jonathan Lipps
Jonathan Lipps
@boneskull figured this out with TSDoc
It looks like the execute atom never returned. Maybe `document.readyState` is not accessible or something on your webpage? At any rate we just updated the atoms, so try again with...
Sorry, no update
I'm working on this
@pturchinetz the cleanest thing to do would be to create a plugin that handles the actions command and then rewrites the data into the older format and proxies it to...
or i guess since it's really just for the windows driver, and since we know WAD is the only proxy target, you could just implement the actions command in the...
Something like that, but it should be `driver.executeScript`
Unfortunately the bug, whatever it is, appears to be in the selenium atoms, but the atoms have changed so much that it is a big project to update them in...
@StephanLuis I've finally incorporated a new version of the Selenium atoms into the XCUITest driver. It's several years newer, so maybe it has a fix for these issues? Please try...