ropensci / RSelenium

An R client for Selenium Remote WebDriver
https://docs.ropensci.org/RSelenium
343 stars 81 forks source link

setImplicitWaitTimeout fails "Cannot call non W3C standard command while in W3C mode" #244

Open yogat3ch opened 3 years ago

yogat3ch commented 3 years ago

Hi RSelenium devs, RSelenium has come a long way in the last three years! Thank you all for you work on it. It's far less cumbersome to use now that I can launch without creating a docker container, and using TightVNC to view the browser window!

Operating System

Windows 10 Home 10.0.19042

Selenium Server version (selenium-server-standalone-3.0.1.jar etc.)

Unsure - whatever is bundled with RSelenium 1.7.7.

Browser version (firefox 50.1.0, chrome 54.0.2840.100 (64-bit) etc.)

Chrome 89.0.4389.82 (Official Build) (64-bit)

Other driver version (chromedriver 2.27, geckodriver v0.11.1, iedriver x64_3.0.0, PhantomJS 2.1.1 etc.)

From the error message: Build info: version: '4.0.0-alpha-2', revision: 'f148142cf8', time: '2019-07-01T21:30:10'

Expected behaviour

Current code is as follows

eCaps <- list(chromeOptions = list(
    args = list('--disable-notifications')
  ))
  chrome <- RSelenium::rsDriver(browser = "chrome", port = 5901L, extraCapabilities = eCaps)
  rD <- chrome$client
  rD$setImplicitWaitTimeout()

I would expect this to set the implicit wait timeout to 10 seconds.

Actual behaviour

This error is thrown:

Selenium message:unknown command: Cannot call non W3C standard command while in W3C mode
Build info: version: '4.0.0-alpha-2', revision: 'f148142cf8', time: '2019-07-01T21:30:10'
System info: host: 'STEPHEN-PC', ip: '172.30.80.1', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_271'
Driver info: driver.version: unknown

Error:   Summary: UnknownCommand
     Detail: The requested resource could not be found, or a request was received using an HTTP method that is not supported by the mapped resource.
     class: org.openqa.selenium.UnsupportedCommandException
     Further Details: run errorDetails method

Steps to reproduce the behaviour

Code above should reproduce the behaviour.

Additional details:

This SO Post indicates that setting w3c = FALSE as an experimental option can potentially resolve this issue, but I'm unsure as to how to go about declaring that option to the driver with RSelenium and would welcome instruction in that regard

With appreciation for any advice on this issue