miksch123
miksch123
Does maybe someone know why this behavior is happening with Google's Chrome Browser? Maybe it is something obvious that I just can't grasp.
Might starting the Mac driver using process.start or a similar approach be an option to solve this?
I wonder if it is possible to use seleniums action class to send enter or tab key...
When you are firstly starting the app it blocks you from running it. When that happens go to settings > security & privacy in there you should see the blocked...
Have you tried it using a webdriver wait? I ran into a similar issue and adding a wbdriverwaiter to wait for the element to appear actually helped there. (And yes...
new WebDriverWait(driver, TimeSpan.FromSeconds(20)).Until(X => X.FindElement(By.XPath("element/you/found/using/afm"))); Here you go. This is a c# example as I am using that mainly.
If I am correct then the selenium dependency for winium would need to be updated to version 3 (ideally 3.141.0) and a dispose methods should be implemented in the necessary...
What you can do is do it the other way round. Start chrome using the chrome webdriver and then Interact with the existing window through winium
There is the output of my dotnet info command: .NET Core SDK (reflecting any global.json): Version: 3.1.417 Commit: e22a5e10f1 Runtime Environment: OS Name: Windows OS Version: 10.0.19044 OS Platform: Windows...
Probably as there is no response that it didn't work.