Apr 11 2019 04:55 AM
Apr 11 2019 04:55 AM
since ChromiumEdge is now available as a canary and a dev version I am also all to curious about how selenium will come into play as it is basically a chromium browser. What webdriver will people use? Is it the edge driver or the chrome driver or a completely new one?
Also how far off will be automating ChromiumEdge when it comes to coding best practises?
Hopefully this is a good start for a thought.
Apr 14 2019 11:53 AM - edited Apr 14 2019 11:53 AM
Hi @mmiky123, thank you for taking the time to play around with the preview channels of the Microsoft Edge browser. We are looking into the automation story for our new browser, and will be talking about it when it is ready. In the meantime, I have captured your feedback and have given it to the right team.
Apr 17 2019 07:16 PM
@mmiky123, I also wanted to let you know that we will have an MSEdgeDriver available very soon. It will have a download link and should also be in a chocolatey package. For the time being, you can point the ChromeDriver to the msedge.exe binary. One challenge there is that Selenium checks for the Browser version and will throw an error, so you ALSO have to modify the python script in Selenium. If you know how to do that, go for it. If not, you can wait just a little bit of time.
Apr 18 2019 11:23 AM
Apr 19 2019 02:26 PM
@johnjansen Thank you, I have been looking for the new webdriver for Chromium Edge as well. I have attempted pointing the latest ChromeDriver (74.0.3729.6) at Edge but it appears version checking is being performed by ChromeDriver itself ("unrecognized Chrome version: Edg/18.104.22.168"). Circumventing this would require compiling a new ChromeDriver from the Chrome repo, which at that point it makes more sense to just wait for your dedicated driver.
Apr 24 2019 06:29 AM
@DaleRiechert2& for those who are curious - it would require to patch this file , like done for the headless mode in .
Anyone has already a Chromium build infrastructure set up and can quickly compile such a binary until we have an official build (From my experience it might take a while to wait...)?
Apr 24 2019 08:22 AM
@BPascal the official builds will be out today. As soon as we get the links cleaned up and merged, I'll post a link to the download page.
Apr 24 2019 11:32 AM
@johnjansen @BPascal the link is now live!!! https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/#downloads
Apr 26 2019 02:36 AM
Apr 26 2019 02:47 AM
Apr 26 2019 08:53 AM
@mmiky123 glad to hear that. Yeah, we need to get our language bindings merged into Selenium to avoid the rename. I forgot to mention that. Glad your test worked, though!
Apr 29 2019 01:19 AM
Apr 29 2019 06:07 AM
Apr 29 2019 08:35 AM
@BPascal that's great feedback, thanks. I will log a bug and make this change so the URL will include the version number that it links to.
May 07 2019 07:22 AM - edited May 07 2019 07:31 AM
@johnjansenGreat. Will the msedgedriver for macOS also be made available for download on the given webpage? Using the standard chromedriver here again fails (as with Windows) with the message:
org.openqa.selenium.WebDriverException: unknown error: unrecognized Chrome version: Edg/22.214.171.124
Jul 08 2019 12:30 AM
Hy @johnjansen. I want to ask if you can help me with some information about msedgedriver for macOS. I tried to use msedgedriver with canary for ma os, the versions are the same, but I get an error message on autotest with selenium. There is any info about this, or it will be a stable version (because this one is beta?). Thank you very much for your help.
Jul 08 2019 08:10 AM
@Handariel what is the error you're getting? I have not heard of any errors on Mac yet, so this could be interesting.
Jul 16 2019 02:57 PM - edited Jul 16 2019 02:58 PM
Please help me understand here, the only action taken here is to rename msedgedriver.exe to chromedriver.exe? Rest entire code remains the same as if we were using chromedriver? If so is the case can you please help me understand what to expect when we launch broswer
? Are we expecting chrome or edge to launch when ran in non headless mode?