Microsoft Edge for Mac Comes to the Dev Channel

Posted on June 6, 2019 by Paul Thurrott in Mac and macOS, Microsoft Edge with 5 Comments

Mac users who are interested in testing the new Chromium-based Microsoft Edge now have a second pre-release channel from which to choose.

“You can now download the Dev channel for macOS from the Microsoft Edge Insider website,” Microsoft revealed this week. “This release enables dark mode, which makes your tabs, address bar, toolbar, menus, and other elements use dark colors if you have your macOS theme set to Dark Mode. We’ll expand dark mode in the coming weeks to include other parts of Microsoft Edge, such as settings and management pages.”

Microsoft originally released the new Edge only for Windows 10, and on that platform, users can choose between the Dev channel, which provides weekly updates, and the Canary channel, which is updated nightly. The first Mac release came next, but it was initially available only in Canary. So with the availability of the Dev channel, Mac users now have a more stable version to test if they prefer to do so.

That said, my experience with the Mac version of Microsoft Edge mirrors of that on Windows 10: It’s very stable, feature-rich, and works quite well. The only major missing bit, really, is full settings sync. Right now, the browser only syncs Favorites (on both platforms).

Still waiting in the wings, of course, is Microsoft Edge for both Windows 7 and 8.x, and the availability of Beta channel builds, which will be updated monthly and be even more stable.

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (5)

5 responses to “Microsoft Edge for Mac Comes to the Dev Channel”

  1. rfog

    Still using 80% of CPU usage when idle and closed?

  2. curtisspendlove

    I've been running Canary since it was first offered and it's been extremely stable. Not a single crash on any of my Macs. The "Hold Command-Q to Quit" thing annoys the hell out of me though; but I don't blame Microsoft for that.