Edge 136 Beta Release: Enhanced Settings and Features

Edge 136 Beta Release: Enhanced Settings and Features

Microsoft Edge Beta Update: Version 136.0.3240.8

Microsoft has recently rolled out a significant update for Edge Insiders, specifically targeting those in the Beta Channel. This update, designated as version 136.0.3240.8, introduces numerous enhancements aimed at improving user experience in the browser’s settings. Notable changes include enhancements to navigation options, alerts, profile visibility, a newly designed extensions page, and a variety of other features.

Changelog Overview

Below are the key features and changes introduced in this update:

  • Updated Edge Update Alerts: Users will notice a new badge that appears in the Settings and More menu (“…”) signaling when updates for Microsoft Edge are available.
  • Performance and Security Enhancements: The Settings and More menu has been restructured to improve accessibility to update alerts. Additionally, browser essentials are now categorized into two separate experiences—Performance and Secure Network—both accessible from the menu. Note: This is being rolled out gradually, so availability may vary.
  • Profile Visibility in Toolbar: To maximize the usability of the tab strip, especially when multiple tabs are open, the Profile pill has been moved to the toolbar. It will now display as a minimized icon by default. Network administrators can adjust this setting according to organizational branding requirements without affecting pre-existing configurations.
  • New Password Management Policy: The browser now features the PasswordExportEnabled policy, which allows administrators to dictate the availability of the Export Password button in the edge://wallet/passwords interface. When disabled, users will not have the option to export passwords.
  • Updates to HTTPS Policies: The AutomaticHttpsDefault policy has been deprecated starting with version 136 and will be replaced in version 139 by the new HttpsUpgradesEnabled policy, which is currently available.
  • Secure Password Deployment Feature: Organizations can now use the secure password deployment feature via the Edge management service, allowing for encrypted shared passwords to be deployed to users, enhancing security without revealing actual passwords. This feature is still in public preview and requires opting into targeted releases through the Microsoft 365 admin center.
  • Improved Settings Navigation: Microsoft Edge has introduced streamlined navigation within its settings. While all existing functionalities remain intact, key settings will now feature clickable sections for easier access. This includes:
    • A quick access segment at the start of the Settings page that guides users directly to commonly used actions.
    • Enhanced navigation on densely populated settings pages (such as privacy and performance settings), allowing users to access specific actions with fewer clicks.
    • A “table of contents”structure for lengthy settings sections, improving navigability and minimizing scrolling.
  • Extension Management Improvements: Users can now find and manage installed extensions more easily with the addition of a dedicated “Extensions”navigation menu and search function within Browser Settings (edge://settings).Note: Like other features, this is part of a gradual rollout and may not be available to all users immediately.

Additional Enhancements

Beyond the major updates mentioned, Edge 136 in the Beta Channel also includes refinements from previous Dev Channel feature updates. Users can explore the details of these improvements through the following links:

Explore Edge 136 Beta

For users eager to experience the latest features of Edge 136 in the Beta Channel prior to its official Stable Release scheduled for the week of May 1, you can download it from the official Edge Insider website. This version can be used side-by-side with the stable iteration and other preview releases compatible with Windows, macOS, Linux, and Android.

Source & Images

Leave a Reply

Your email address will not be published. Required fields are marked *