Microsoft WebDriver support
See original GitHub issueHello,
Can anybody confirm that canopy works with MS Edge driver (17134)?
Getting The remote server returned an error: (400) Bad Request.
with the most recent Windows. Not sure if the problem is with canopy or with the webdriver.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Use WebDriver to automate Microsoft Edge
Selenium uses the EdgeDriverService class to manage an Microsoft Edge WebDriver process. You can create an EdgeDriverService once before running ...
Read more >Edge specific functionality
Microsoft Edge is implemented with Chromium, with the earliest supported version of v79. Similar to Chrome, the major version number of ...
Read more >How to launch Edge browser in Selenium
Configuring the Edge Driver · The primary step is to check the version of the OS build being used. · To check the...
Read more >Using python selenium for Microsoft edge
You first check wich version your edge is and then download de Edge driver from Microsoft Page · Download and unzip the msedgedriver...
Read more >How To Download And Setup Edge Driver For Selenium
Microsoft offers a Selenium WebDriver for automating the Microsoft Edge browser called Edge Driver. It acts as a bridge for seamless ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Good thing about “localhost” is that it works with all major browsers (except Safari, haven’t tried it yet). Speed issue is important though.
Thank you for your time and explanations.
For build.fsx, I can’t remember if I use it anymore with .net core, so don’t worry about that.
I added
configuration.driverHostName <- "localhost"
because in .net core it can’t resolve localhost correctly and it made every call to selenium have an additional 1 second added to it, making tests crazy slow. That setting is used by selenium to know what address to talk to the webdriver over.http://127.0.0.1:19123 or http://localhost:19123
. I set it to use 127.0.0.1 to make dotnet core work at the correct speed, but apparently that breaks edge.