The latest version of Selenium (3.141.59) throws errors for the said interface. We posted a question on Stack Exchange regarding this. Looking at the answer, we now know there is a new package/interface is available for the same. Perhaps changing the import statements to use this package might resolve the issue.