Edge is, now, Series 132❗
Your browser has been updated to the newest version.Microsoft Edge is your AI-powered browser.Discover new Copilot in Edge features.
Version 132.0.2957.115: January 17, 2025
Fixed various bugs and performance issues, Dev channel updates, feature updates, policy updates, and site compatibility impacting changes.
Stable channel security updates are listed here.
Fixes
- Fixed an issue on macOS that caused rendering issues and missing text when viewing certain PDF files containing Japanese fonts.
Feature updates
- Intune policies in the Microsoft Edge management service. Admins now can set Intune policies via the Microsoft Edge management service, alongside the existing cloud policies. This ability lets admins deploy both browser policies in the cloud and Intune policies from a single pane, making it easy to keep users safe and the browser workflow streamlined. This feature comes along with a new policy creation wizard that streamlines the creation process into a comprehensive, step-by-step flow. Note: This experience is in public preview and can be accessed by opting in to targeted release in the Microsoft 365 admin center.
- Version monitoring in the Edge management service. The Edge management service offers a single view of all managed Edge instances with their update status and possible actions to take. For out-of-date devices, you can easily schedule updates or notify users to update their browsers to avoid workflow interruptions. Note: This experience is in public preview and can be accessed by opting in to targeted release in the Microsoft 365 admin center.
- Shopping Product Tracking. Track product prices easily with a new experience in the Edge Address Bar that appears on the product detail page. Users can track prices quickly and are notified when there's a price drop on that product and save more. Administrators can control the availability of Shopping in Edge using the EdgeShoppingAssistantEnabled policy. Note: This feature is a controlled feature rollout. If you don't see this feature, check back as we continue our rollout.
- New password manager policy. The DeletingUndecryptablePasswordsEnabled policy controls whether the built-in password manager can delete undecryptable passwords from its database. This policy is required to restore the full functionality of the built-in password manager, but it might cause permanent data loss. Undecryptable password values won't become decryptable on their own. If fixing them is possible, it usually requires complex user actions.
- PromotionalTabsEnabled policy deprecation. The PromotionalTabsEnabled policy is deprecated in Microsoft Edge version 132 and will be obsolete in a future Microsoft Edge version. Administrators can use the ShowRecommendationsEnabled policy instead.
- Allow enterprise users to view XFA PDFs using IE Mode. Enterprise customers can view XFA PDFs in Microsoft Edge using IE mode through either the ViewXFAPDFInIEModeAllowedOrigins or ViewXFAPDFInIEModeAllowedFileHash policy. This change will be available in the new PDF viewer on Microsoft Edge.
- Deprecation of Microsoft Edge Support page. To improve end user experience, edge://support is being deprecated. The information found on edge://support is available on other pages: edge://version, edge://metrics-internals, edge://extensions, and edge://policy.
- Full Favorites Bar available in Workspaces. Workspaces now display a user's full set of favorites in the Favorites Bar, with a dedicated workspace folder accessible from the bar. Previously when in a workspace, a user's existing Favorites Bar was not easily accessible and instead only the workspace favorites folder was visible. Users can control the behavior by modifying #edge-workspace-favorites-bar in edge://flags.
Policy updatesNew policies
Deprecated policies
Obsoleted policies
Site compatibility impacting changes
- Removal of old Headless from the Edge binary. Running Edge with
--headless=old no longer launches the old Headless mode, and instead prints the following log message: Old Headless mode has been removed from the Chrome binary. Please use the new Headless mode or the chrome-headless-shell which is a standalone implementation of the old Headless mode.
- CSS Anchor Positioning: allow
anchor-size() in inset and margin properties. Originally, anchor-size() was only allowed in sizing properties. The specification now allows anchor-size() in insets and margins as well.
- CSS sideways writing modes. Support of
sideways-rl and sideways-lr keywords for the writing-mode CSS property. sideways-rl and sideways-lr are helpful to write non-CJK text vertically. They don't have behaviors favorable for CJK languages unlike vertical-rl and vertical-lr.
- Dialog toggle events. This change incorporates the same
ToggleEvent that popovers dispatch, but for <dialog> elements: when showModal or show is called, <dialog> dispatches a ToggleEvent with newState=open. When a <dialog> is closed (using the form, button, or closewatcher) it should dispatch a ToggleEvent with newState=closed. Previously, to detect when a <dialog> opens a mutation observer had to be registered to check for open.
- Element Capture. Given a video
MediaStreamTrack obtained through pre-existing means to initiate tab-capture, Element Capture allows mutating the track to only capture a subtree of the DOM starting at a given Element. The API bears some resemblance to the Region Capture API, but affords greater flexibility for applications, because occluding and occluded content are both excluded from the capture.
- FedCM authorization features. This bundles a few features that Identity Providers (IdP) can use to implement authorization flows such as letting a user grant access to their calendar to a Relying Party (RP). Specifically:
- The IdP needs to be able to show a custom prompt for the permission (continuation API).
- The RP needs an extensible way to communicate to the IdP what it wants access to (parameters API).
- The RP needs to be able to customize or suppress the text referring to the IdP sharing "name, email address, and profile picture" because in this situation they're asking for different information (fields API).
- The IdP might want to use a different endpoint to implement the authorization flow (multiple configURLs).
- Certain accounts may only be eligible for one of the authentication and authorization flows and so there needs to be a way to show different accounts in the two flows (account labels API).
- FedCM Mode API and Use Other Account API. Two new extensions for FedCM:
- Mode: The
active mode allows websites to call FedCM inside a button click (for example, selecting a Sign-in to IdP button), which requires FedCM to guarantee it always responds with a visible user interface. Calling the FedCM API in active mode takes users to sign in to the Identity Provider (IdP) when users are logged-out. Also, because the active mode is called within an explicit user gesture, the UI is also more prominent (for example, centered and modal) compared to the UI from the passive mode (which doesn't require a user gesture requirement and can be called on page load).
- Use Other Account: With this extension, an IdP can allow users to sign in to other accounts.
- Fetch:
Request.bytes() and Response.bytes(). Add a bytes() method to the Request and Response interfaces, which returns a promise that resolves with a Uint8Array. While Request and Response have an arrayBuffer() method, it’s not possible to read directly from a buffer. A view such as a Uint8Array must be created to read it. The bytes() method improves the ergonomics of getting the body of Request and Response.
- Ignore Strict-Transport-Security for localhost.
Strict-Transport-Security (STS) response headers can cause problems for localhost web servers because STS applies host-wide, across all ports. This causes compatibility problems for web developers testing locally. It also affects end-users who use software packages that commonly start localhost web servers for ephemeral reasons. For example, communication of an auth token from a web sign-in to a local software package. If one local listener sets Strict-Transport-Security on a localhost response, it's applied to all subsequent localhost requests regardless of port. Edge 132 resolves this problem by ignoring Strict-Transport-Security headers on responses from localhost URLs.
- Keyboard focusable scroll containers. The rollout of this feature (from Edge 130) was stopped due to an accessibility regression. This issue is fixed and the feature continues to rollout with Edge 132. KeyboardFocusableScrollersEnabled is the policy for this feature.
- Private State Token API Permissions Policy default allowlist wildcard. Access to the Private State Token API is gated by Permissions Policy features. Edge 132 updates the default allowlist for both
private-state-token-issuance and private-state-token-redemption features from self to * (wildcard).
-
PushMessageData::bytes(). The PushMessageData interface mimics the Body interface, which was amended earlier this year with a new bytes() method, following the principle that APIs should generally vend byte buffers as Uint8Arrays. Edge 132 realigns with the Body interface by providing the bytes() accessor on the PushMessageData interface as well.
- Saved queries in
sharedStorage.selectURL. sharedStorage.selectURL() now lets queries to be saved and reused on a per-page basis. Two per-page-load budgets are charged the first time a saved query is run but not for subsequent runs of the saved query during the same page-load. This change is accomplished with a savedQuery parameter in the options for selectURL() that names the query.
- Throw exception for popovers and dialogs in non-active documents. Previously calling
showPopover() or showModal() on a popover or dialog that resides within an inactive document would silently fail. No exception was thrown, but since the document is inactive, no popover or dialog would be shown. As of Edge 132, these situations now throw InvalidStateError.
- WebAuthn Signal API. Allows WebAuthn relying parties to signal information about existing credentials back to credential storage providers, so that incorrect or revoked credentials can be updated or removed from provider and system UI.
- WebGPU: 32-bit float textures blending. The
float32-blendable GPU feature makes GPU textures with formats r32float, rg32float, and rgba32float blendable.
- WebGPU: Expose GPUAdapterInfo from GPUDevice. The GPUDevice
adapterInfo attribute exposes the same GPUAdapterInfo as the GPUAdapter object.
- WebGPU: Texture view usage. Adds an optional field to WebGPU texture view creation to request a subset of the usage flags from the source texture. By default, texture view usage inherits from the source texture but there are view formats that can be incompatible with the full set of inherited usages. Adding a usage field to texture view creation allows the user request a subset of the source texture's usages that are valid with the view format and specific to their intended usage of the texture view. WebGPU implementations can also optimize the creation of low level resources and improve performance when using views with more specialized usage flags.
- New origin trials: Document-Isolation-Policy. The Document-Isolation-Policy lets a document enable
crossOriginIsolation for itself, without having to deploy COOP or COEP, and regardless of the crossOriginIsolation status of the page. The policy is backed by process isolation. Additionally, the document non-CORS cross-origin subresources will either be loaded without credentials or will need to have a CORP header.
- New origin trials: Explicit Compile Hints with Magic Comments. This feature lets you attach information about which functions should be eager parsed and compiled in JavaScript files. The information will be encoded as magic comments.
-
navigator.storage no longer an EventTarget. navigator.storage was made an EventTarget for the Storage Pressure Event, which never made it past the prototype phase. This dead code is being removed and as a result, navigator.storage will no longer extend EventTarget.
- Remove Prefixed HTMLVideoElement Fullscreen APIs. The prefixed HTMLVideoElement fullscreen APIs have been deprecated from Edge. They were replaced by the
Element.requestFullscreen() API. As of 2024, most browsers have had support for the unprefixed APIs for a few years now. Edge 132 removes the following from HTMLVideoElement:
- The
webkitSupportsFullscreen attribute.
- The
webkitDisplayingFullscreen attribute.
- The
webkitEnterFullscreen() method.
- The
webkitExitFullscreen() method. Note the different capitalization of the "S" in FullScreen.
- The
webkitEnterFullScreen() method.
- The
webkitExitFullScreen() method.
These methods are now only aliases for the modern API. Their use has declined steadily over the years.
Cheers,
Drew![Image](https://learn-attachment.microsoft.com/api/attachments/53b77890-8bbf-498b-bc01-a2677b397aba?platform=QnA
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 34%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
