When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

This week's Edge Dev build focuses on fixes, prepares the next Beta release

As usual on Tuesdays, Microsoft has released a new build of the Chromium-based Edge browsers to Insiders enrolled in the Dev channel. This time, we're getting build number 79.0.309.5, and you may notice that the build number is only one number higher than last week's build, which was 79.0.308.1. That's because Microsoft has mostly focused on making fixes and improvements, since this build is the candidate for the next release of Edge in the Beta channel.

The changelog is much smaller than usual for this release, so much so that Microsoft isn't splitting up the new changes into different categories and just lists them all in one go. Here are all the fixes and improvements in this release:

  • Fixed a crash when logging into the browser.
  • Fixed an issue where typing in the address bar sometimes causes the browser to crash.
  • Fixed an issue where the browser sometimes crashes after completing the first run experience.
  • Fixed a hang during the first run experience.
  • Fixed an issue where the theme sometimes changes unexpectedly after the first run experience.
  • Fixed some issues with Application Guard windows not successfully opening.
  • Disabled hardware acceleration in Application Guard windows to prevent them from hanging on certain machines.
  • Fixed an issue where certain webpages don’t open in Application Guard windows even though they should.
  • Fixed an issue where files that should be downloaded in Application Guard windows aren’t.
  • Fixed an issue where an extra “Work” browser profile gets automatically created for some users (note that this may not remove the extra profile; a future fix will ensure that).
  • Fixed an issue where the Mac Touch Bar sometimes doesn’t show the proper content.
  • Fixed an issue where the Settings page constantly shows “looking for updates” without ever completing.
  • Fixed an issue where certain settings are changeable even when they’re disabled.
  • Fixed an issue where certain settings that are supposed to be enabled by default are disabled after performing a settings reset.
  • Fixed an issue where the Delete button does not appear next to downloads that have been blocked by SmartScreen.
  • Fixed an issue where the warning not to close the browser because a download is in progress appears even though the user isn’t downloading anything.
  • Fixed an issue where websites that are blocked by SmartScreen aren’t removed from history.
  • Improved scrolling behavior on the new tab page.
  • Fixed some issues with the PDF toolbar’s hiding behavior.
  • Fixed an issue where switching between IE mode tabs and non-IE mode tabs leaves webpages at the wrong zoom level on certain devices.
  • Fixed an issue where no sites open in IE mode tabs when a certain combination of IE mode policies is applied.
  • Fixed an issue where tooltips in Collections all say “collection content” instead of the actual content.
  • Fixed an issue where certain print preview content is hard to read in dark theme.

When this release hits the Beta channel, it'll be the third build of the browser to officially be labeled as Beta, however, there is still no clear release date for a stable version of the Chromium-based Edge. In the meantime, users in the Canary channel have begun testing the first builds based on Chromium 80 this week, and those in the Dev channel will likely see that in next week's release.

Report a problem with article
Next Article

Razer announces Hammerhead True Wireless earbuds

Previous Article

Radical Technologies - free book summary

Join the conversation!

Login or Sign Up to read and post a comment.

7 Comments - Add comment