First Edge 95 build for the Dev channel brings inking improvements and many fixes

Microsoft today released the first Edge 95 build for the Dev channel, bringing a couple of new features and a bunch of improvements to the browser. The last build for the Dev channel released last week was the final build for version 94, which means that the firm is readying to release that version to the Beta channel sometime this week. The latest build also follows the new 4-week update cadence, meaning that the flights will be propagated to the Beta channel – and eventually the stable channel – sooner than earlier versions did.

As for today’s build, there is not much in the way of huge features. The firm is adding the ability to use keyboard keys to ink on PDFs and screenshots captured through the in-build web capture tool. Additionally, the browser will also be able to sync payment cards’ data automatically to a Microsoft account via the browser itself. The firm is also highlighting the recently announced WebView 2 updates. Considering that this is the first Edge 95 build for the Dev channel, it is light on features, but there are a bunch of bug fixes, which is always welcome.

As usual, the bug fixes are categorized into reliability improvements and fixes that address changed behavior. This week, the company has listed the improvements for the mobile client within a separate bullet point, giving a consolidated list for mobile alone, for those interested.

Here are all the reliability improvements:

• Fixed an issue where interacting with autofill popups sometimes crashes the browser.
• Fixed a crash when dragging tabs between windows.
• Fixed a tab crash.
• Fixed a crash when closing tabs that contain Office documents.
• Fixed a crash when editing saved passwords in Settings.
• Fixed a crash on Mac when the management policy to Force Sign In is provisioned.
• Mobile issues:
  • Fixed a crash when organizing favorites.
  • Fixed a crash when deleting a favorite.
  • Fixed a crash on launch.
  • Fixed a crash when signing out of the browser.
  • Fixed an issue where the browser fails to open.
  • Fixed a hang when navigating to malicious sites that are blocked by SmartScreen.
• Fixed an issue where WebView2 apps sometimes crash soon after launching (Issue 1678).

And here are the fixes that address changed behavior:

• Fixed an issue where searching Settings causes it to go blank.
• Fixed an issue where some Settings can’t be searched for.
• Fixed an issue where profiles get signed out or duplicated after updating the browser.
• Fixed an issue where a custom scale when printing isn’t retained between prints.
• Fixed an issue where the option to change a password in Password Settings doesn’t do anything.
• Fixed an issue where Rebates sometimes fail to be applied.
• Fixed an issue where Rebates sometimes fail with an error.
• Fixed an issue where Coupons sometimes aren’t found when they should be.
• Fixed an issue where the Web Widget doesn’t display properly.
• Fixed an issue where the Web Widget is missing some UI.
• Fixed an issue where MHT files sometimes don’t render properly.
• Mobile issues:
  • Fixed an issue where the preference for desktop vs. mobile sites is sometimes reset after installing an update.
  • Fixed an issue where signing into the browser sometimes fails for work and school accounts.
  • Fixed an issue where navigating to certain websites takes an inordinate amount of time.
• WebView2 issues:
  • Fixed an issue where a white flash sometimes appears when loading dark content (Issue 1621).
  • Fixed an issue where more DLLs than necessary are sometimes added to projects (Issue 709).
  • Fixed an issue where the wrong certificate is sometimes selected from the ClientCertificateRequested event (Issue 1666).
  • Fixed an issue where a WebView object is sometimes not defined properly (Issue 1144).
  • Fixed an issue where minimizing a WebView2 application sets focus incorrectly (Issue 238).
  • Fixed an issue with error handling.

As usual, the Redmond company has listed the known issues that it is aware of in the browser. This is handy for those who might want to switch to a more stable version if their workflow is broken due to these issues. As with every week, some of these issues have had their place on the list for a long time. Here is the complete list:

• Users of certain ad blocking extensions may experience playback errors on Youtube. As a workaround, temporarily disabling the extension should allow playback to proceed. See this help article for more details.
• Some users are still running into an issue where all tabs and extensions immediately crash with a STATUS_INVALID_IMAGE_HASH error. The most common cause of this error is outdated security or antivirus software from vendors like Symantec, and in those cases, updating that software will fix it.
• Users of the Kaspersky Internet Suite who have the associated extension installed may sometimes see webpages like Gmail fail to load. This failure is due to the main Kaspersky software being out of date, and is thus fixed by making sure the latest version is installed.
• Some users are still seeing favorites get duplicated. This issue should be reduced now that automatic deduplication has been introduced into Insider channels, but we’re still rolling that out in Stable. We’ve also seen duplication happen when running the manual deduplicator on multiple machines before either machine has a chance to fully sync its changes, so make sure to leave plenty of time in between runs of the deduplicator.
• Some users are seeing “wobbling” behavior when scrolling using trackpad gestures or touchscreens, where scrolling in one dimension also causes the page to subtly scroll back and forth in the other. Note that this only affects certain websites and seems to be worse on certain devices. This is most likely related to our ongoing work to bring scrolling back to parity with Edge Legacy’s behavior, so if this behavior is undesirable, you can temporarily turn it off by disabling the edge://flags/#edge-experimental-scrolling flag.

As mentioned earlier, those running Beta builds of the Edge browser should receive version 94 later this week. Edge 93 should also soon make it to the stable channel. As for today’s build, it will begin rolling out gradually, meaning not all users will be able to pull the update via the About Microsoft Edge settings page right away.

First Edge 95 build for the Dev channel brings inking improvements and many fixes