(http://i.postimg.cc/jj7Gjwrm/cedge-1-1.png)
Microsoft published an extensive FAQ (http://github.com/MicrosoftEdge/MSEdge) on their plans to move the Edge browser from EdgeHTML to Google’s Chromium rendering engine, but in the three thousand word article did not reveal the best benefit from the move to Chromium.
Posting on Reddit however, Kyle Alden, Project Manager for Edge, revealed that the new Edge will indeed provide support for Google Chrome Extensions, saying:
It’s our intention to support existing Chrome extensions.
(http://i.postimg.cc/2SvqFGd5/Capture4.png) (http://www.reddit.com/r/Windows10/comments/a3pt19/microsoft_edge_making_the_web_better_through_more/?utm_term=31154799821&utm_medium=comment_embed&utm_source=embed&utm_name=567cbebc-fae0-11e8-b6ee-0e4cbfb3ac68&utm_content=more)
The posting also confirms that UWP developers need not worry about the move disrupting their applications, as the EdgeHTML rendering engine will remain the default for their application until they make the conscious move to the new Chromium Webview rendering engine.
This move will close the Extension “app gap” between Chrome and Edge, and will make it easier for users to move between the browsers, meaning Microsoft will have less excuse for not winning users over. Hopefully, Microsoft will now step up with a more usable browser that matches Chrome feature for feature.
source (http://mspoweruser.com/microsoft-kept-quiet-about-the-best-part-of-moving-edge-to-chromium/)