Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • @Jcyrss Checkout the updated answer and let me know if you have any questions. Commented Jan 27, 2020 at 10:12
  • 1
    thank you. But it seems it all about the interface between WebDriver and Driver(like ChromeDriver), not the interface between Driver (like ChromeDriver) and Browser (like Chrome) Why I'm curious about that? MicroSoft bring us Chromium based Edge Browser, we need to automate it with Selenium. As I known, Chromium has built-in web automation support (that's true because we could automate Electron App with Chromedriver). I want to know why bother MS provides Edge driver if existing ChromeDriver already could drive Chromium based Browser? Commented Jan 28, 2020 at 2:15
  • @Jcyrss I am sure you haven't read the complete answer. However your question involving Chromedriver act as a HTTP server, ChromeDriver communicate with Chrome and HTTP protocol is overly broad as per stackoverflow standards and I shouldn't have answered in the first place. Now as you have added more questions with respect to interface between Driver (like ChromeDriver) and Browser (like Chrome), Chromium based Edge Browser and Electron App, and an answer would be too big as per the space provided by SO. Commented Jan 28, 2020 at 6:55
  • 1
    I don't think I asked too broad question. And again I don't think this post anwsered my question. Because I finally found the true anwser. Chrome driver controls chrome through Chrome DevTools Protocol which based on websocket. This article gives more details Commented May 20, 2020 at 15:16