main to live - Oct 9, 2025

microsoft-edge/devtools/whats-new/2025/10/devtools-141.md

@@ -0,0 +1,55 @@
+---
+title: What's New in DevTools (Microsoft Edge 141)
+description: CSS masonry layout support in the Elements tool. Persisted track configuration in the Performance panel. And more.  # key words before col 158
+author: MSEdgeTeam
+ms.author: msedgedevrel
+ms.topic: conceptual
+ms.service: microsoft-edge
+ms.subservice: devtools
+ms.date: 10/02/2025
+---
+# What's New in DevTools (Microsoft Edge 141)
+
+These are the latest features in the Stable release of Microsoft Edge DevTools.
+
+
+<!-- ====================================================================== -->
+## CSS masonry layout support in the Elements tool
+
+<!-- Subtitle: Inspect masonry layout in the Layout tab and adorners in the DOM tree. -->
+
+CSS masonry layout is supported in the **Layout** tab of the **Elements** tool.  Masonry layout elements are displayed alongside grid layout elements:
+
+![The Grid/Masonry section in the Layout tab](./devtools-141-images/masonry-layout-tab.png)
+
+In the **Overlay display settings** section, you can control whether to display:
+* Line numbers or line names.
+* Track sizes.
+* Area names.
+
+The **masonry** adorner appears next to elements in the DOM tree, similar to the **grid** or **flex** adorners:
+
+![The "masonry" adorner on the body tag in the DOM tree](./devtools-141-images/masonry-adorner.png)
+
+See also:
+* [Inspect CSS Grid](/microsoft-edge/devtools/css/grid)
+* [CSS Masonry demos](https://github.com/MicrosoftEdge/Demos/tree/main/css-masonry)
+* [Brick by brick: Help us build CSS Masonry](https://developer.chrome.com/blog/masonry-update) - Blog post.
+* [Elements > Layout tab adds masonry layout support](https://developer.chrome.com/blog/new-in-devtools-141#masonry) - Chromium What's New.
+
+
+<!-- ====================================================================== -->
+## Announcements from the Chromium project
+
+Microsoft Edge 141 also includes the following updates from the Chromium project:
+
+* [Persisted track configuration in the Performance panel](https://developer.chrome.com/blog/new-in-devtools-141#persisted-track-config)
+* [Filter IP protected network requests](https://developer.chrome.com/blog/new-in-devtools-141#ipp)
+* [Elements > Layout tab adds masonry layout support](https://developer.chrome.com/blog/new-in-devtools-141#masonry)
+
+
+<!-- ====================================================================== -->
+## See also
+
+* [What's New in Microsoft Edge DevTools](../../whats-new.md)
+* [Release notes for Microsoft Edge web platform](../../../../web-platform/release-notes/index.md)

microsoft-edge/toc.yml

@@ -109,6 +109,10 @@
               href: ./devtools/whats-new/whats-new.md
               displayName: release notes, announcements
 # latest 10 What's New
+            - name: Microsoft Edge 141
+              href: ./devtools/whats-new/2025/10/devtools-141.md
+              displayName: What's New in DevTools (Microsoft Edge 141)  # page title
+
             - name: Microsoft Edge 140
               href: ./devtools/whats-new/2025/09/devtools-140.md
               displayName: What's New in DevTools (Microsoft Edge 140)  # page title
@@ -145,16 +149,16 @@
               href: ./devtools/whats-new/2025/01/devtools-132.md
               displayName: What's New in DevTools (Microsoft Edge 132)  # page title
 
-            - name: Microsoft Edge 131
-              href: ./devtools/whats-new/2024/11/devtools-131.md
-              displayName: What's New in DevTools (Microsoft Edge 131)  # page title
-
             # keep 10 items above
             - name: Archive
               items:
                 - name: What's New in DevTools archive
                   href: ./devtools/whats-new/whats-new-archive.md
 
+                - name: Microsoft Edge 131
+                  href: ./devtools/whats-new/2024/11/devtools-131.md
+                  displayName: What's New in DevTools (Microsoft Edge 131)  # page title
+
                 - name: Microsoft Edge 130
                   href: ./devtools/whats-new/2024/10/devtools-130.md
                   displayName: What's New in DevTools (Microsoft Edge 130)  # page title

microsoft-edge/webview2/concepts/distribution.md

@@ -9,6 +9,9 @@ ms.subservice: webview
 ms.date: 06/27/2024
 ---
 # Distribute your app and the WebView2 Runtime
+<!-- todo: mention key words in title:
+# Distribute your app and the WebView2 Runtime (Evergreen vs. fixed)
+-->
 
 When releasing an app that uses Microsoft Edge WebView2, you need to distribute the WebView2 Runtime, either by distributing the automatically updated _Evergreen_ Runtime, or by distributing a _Fixed Version_ of the Runtime.
 

microsoft-edge/webview2/concepts/enterprise.md

@@ -11,9 +11,9 @@ ms.date: 11/12/2021
 # Enterprise management of WebView2 Runtimes
 <!-- old title: # Manage WebView2 applications -->
 
-[WebView2](../index.md) is a component that developers use to build their applications, and the developers can deploy a self-updating Evergreen WebView2 Runtime onto user devices to power their applications.  This article discusses how IT admins can manage WebView2 applications and the WebView2 Runtime.  
+This article discusses how IT admins can manage<!-- todo: define --> WebView2 applications and the WebView2 Runtime.  A developer can integrate the WebView2 component into their app, and then deploy the self-updating Evergreen WebView2 Runtime (along with the app) onto user devices, to power the latest WebView2 features of the app and get the latest security improvements.
 
-Feedback from IT admins and developers is welcome, through the [WebView2 Feedback](https://github.com/MicrosoftEdge/WebViewFeedback) repo.
+Feedback from IT admins and developers is welcome, through the [WebView2Feedback](https://github.com/MicrosoftEdge/WebViewFeedback) repo.
 
 
 <!-- ====================================================================== -->
@@ -25,45 +25,114 @@ IT admins can use group policy objects (GPO) to configure policy settings for We
 <!-- ------------------------------ -->
 #### Update policies
 
-[Microsoft Edge - Update policies](/deployedge/microsoft-edge-update-policies) are available for IT admins to manage the installing and updating aspects of the WebView2 Runtime.  The Microsoft Edge browser and WebView2 Runtime are updated using the same update mechanism.  Unless a policy, such as `Update`, is channel-specific, it applies to both the browser and WebView2 Runtime.
+[Microsoft Edge - Update policies](/deployedge/microsoft-edge-update-policies) are available for IT admins to manage the installing and updating aspects of the WebView2 Runtime.  The Microsoft Edge browser and WebView2 Runtime are updated using the same update mechanism.  The policy applies to both Microsoft Edge and the WebView2 Runtime, unless the policy is channel-specific, such as [Update](/deployedge/microsoft-edge-update-policies#update) and [Update (WebView)](/deployedge/microsoft-edge-update-policies#update-webview).
 
-For example, `UpdateSuppressed` allows IT admins to set the time during each day at which to suppress auto-update for both the browser and WebView2 Runtime.  This enables IT admins to configure preferences and proxies once for both the browser and the WebView2 Runtime, to control their network bandwidth/traffic or for other purposes.
+To configure update policies for Microsoft Edge (and the WebView2 Runtime), see [Configure Microsoft Edge policy settings on Windows devices](/deployedge/configure-microsoft-edge), in the Microsoft Edge Enterprise documentation.
 
-IT admins can follow [Microsoft Edge's guide](/deployedge/configure-microsoft-edge) to configure Microsoft Edge - Update policies.
+
+<!-- ------------------------------ -->
+#### Suppressing WebView2 Runtime updates
+
+An IT admin can suppress updating of the WebView2 Runtime, if auto-updating needs to be suppressed for a short time.  After the time period, updating of the WebView2 Runtime resumes.  The [UpdatesSuppressed](/deployedge/microsoft-edge-update-policies#updatessuppressed) policy allows an IT admin to set the time during each day at which to suppress auto-update for both Microsoft Edge and the WebView2 Runtime.  This enables an IT admin to configure preferences and proxies once for both the browser and the WebView2 Runtime, to control their network bandwidth and traffic, or for other purposes.
+
+However, users should not stop updating their WebView2 Runtime; users should not remain on an older version of the WebView2 Runtime.  Using older versions of the WebView2 Runtime isn't recommended.  Security updates and servicing updates are only available on the latest Stable channel release (Edge Stable) and the latest Beta channel release (Edge Beta).  If you use older releases of the Microsoft WebView2 Runtime, you won't receive the latest quality and security updates.
+
+
+<!-- ---------- -->
+###### Evergreen Runtime is recommended, rather than a fixed version
+
+Using the Evergreen WebView2 Runtime is recommended, unless business-critical requirements necessitate using a fixed version of the WebView2 Runtime.  Using the Evergreen WebView2 Runtime:
+* Helps minimize exposure to known vulnerabilities.
+* Ensures timely security improvements.
+* Ensures that WebView2 benefits from continuous security updates that are delivered through Microsoft Edge releases.
+
+For information about Evergreen vs. fixed version of the Runtime, see [Distribute your app and the WebView2 Runtime](./distribution.md).
+
+For details about security fixes in Microsoft Edge (which apply to WebView2 as well), see [Release notes for Microsoft Edge Security Updates](/deployedge/microsoft-edge-relnotes-security), in the Microsoft Edge Enterprise documentation.
+
+
+<!-- ---------- -->
+###### Rapid Response to Chromium vulnerabilities
+
+To help maintain a secure browsing environment, Microsoft Edge addresses Chromium engine-level vulnerabilities soon after the vulnerabilities are disclosed.
+
+Security fixes address vulnerabilities such as:
+
+* **Remote code execution** – Mitigates risks of arbitrary code execution via malicious content.
+* **Privilege escalation** – Reduces chances of unauthorized system access.
+* **Information disclosure and spoofing** – Protects sensitive data, and helps prevent phishing attacks.
+
+
+<!-- ---------- -->
+###### Microsoft Edge Lifecycle Policy
+
+Microsoft WebView2 follows the Modern Lifecycle Policy.
+
+See:
+* [Modern Lifecycle Policy](/lifecycle/policies/modern), in the Modern Lifecycle Policy documentation.
+* [Microsoft Edge Lifecycle Policy](/deployedge/microsoft-edge-support-lifecycle), in the Microsoft Edge Enterprise documentation.
 
 
 <!-- ------------------------------ -->
 #### Browser policies
 
-[Microsoft Edge - Browser policies](/deployedge/microsoft-edge-policies) doesn't apply to WebView2 applications.  This is by design, because apps and browsers have different use cases, and IT admins might not be aware of what applications use WebView2.  
+[Microsoft Edge - Policies](/deployedge/microsoft-edge-policies) doesn't apply to WebView2 applications.  This is by design, because apps and browsers have different use cases, and IT admins might not be aware of what applications use WebView2.  
 
 Applying browser policies on WebView2 would have unintended consequences.  For example, IT admins can block JavaScript in the browser, and that would break WebView2 apps that use JavaScript.  To prevent that, browser policies are separate from WebView2 policies.
 
 
 <!-- ------------------------------ -->
 #### WebView2-specific policies
 
-[WebView2-specific policies](/deployedge/microsoft-edge-webview-policies) are available to for you<!--dev, or admin?--> to manage WebView2 directly.  However, we recommend that WebView2 app developers implement their own group policies to manage the use of WebView2, because it's easier for administrators to manage the app instead of managing WebView2 directly.
+[Microsoft Edge WebView2 - Policies](/deployedge/microsoft-edge-webview-policies) are available to for you<!--dev, or admin?--> to manage WebView2 directly.  However, we recommend that WebView2 app developers implement their own group policies to manage the use of WebView2, because it's easier for administrators to manage the app instead of managing WebView2 directly.
 
 
 <!-- ====================================================================== -->
-## Windows Server Update Services (WSUS)
+## Windows Server Update Services (WSUS)<!-- todo: deprecated -->
+
+Windows Server Update Services (WSUS) enables IT admins to deploy the latest Microsoft product updates. You can use WSUS to fully manage the distribution of updates of WebView2 that are released through Microsoft Update<!-- todo: "Microsoft Update" vs. "Microsoft Edge updater" --> to computers on your network.
 
-[Windows Server Update Services (WSUS)](/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) enables information technology administrators to deploy the latest Microsoft product updates. You can use WSUS to fully manage the distribution of updates of WebView2 that are released through Microsoft Update to computers on your network.
+See [Windows Server Update Services (WSUS) overview](/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus).
 
-The recommended way of receiving WebView2 updates is by using the default Microsoft Edge updater.  Any modification of update and servicing paths should be done with caution.
+The recommended way of receiving WebView2 updates is by using the default Microsoft Edge updater<!-- todo: "Microsoft Update" vs. "Microsoft Edge updater" -->.  Any modification of update and servicing paths should be done with caution.
 
 
 <!-- ------------------------------ -->
-#### WebView2 Deployment and Update using WSUS
+#### WebView2 deployment and update using Configuration Manager
+<!-- is this option recommended?  is this section details about the above section?  is Configuration Manager indep from WSUS? -->
+
+In Configuration Manager, WebView2 options exist under the **Microsoft Edge Management** node.
 
-WebView2 options in Configuration Manager exist under the Microsoft Edge Management node. For more information, visit [Update Microsoft Edge](/mem/configmgr/apps/deploy-use/deploy-edge).
+See [Update Microsoft Edge](/intune/configmgr/apps/deploy-use/deploy-edge#update-microsoft-edge) in _Microsoft Edge Management_, in the App management documentation.
 
 
 <!-- ====================================================================== -->
 ## See also
-
-* [Distribute your app and the WebView2 Runtime](./distribution.md) - About the Evergreen, self-updating WebView2 Runtime.
-
-<!-- External: -->
-* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)
+<!-- all links in article -->
+
+* [Distribute your app and the WebView2 Runtime](./distribution.md) - Evergreen vs. fixed version of the WebView2 Runtime.
+
+<!-- toc order -->
+Microsoft Edge Enterprise documentation:
+* [Microsoft Edge Lifecycle Policy](/deployedge/microsoft-edge-support-lifecycle)<!-- bucket 2 -->
+* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)<!-- bucket 3 top -->
+* [Release notes for Microsoft Edge Security Updates](/deployedge/microsoft-edge-relnotes-security)<!-- bucket 3 bottom -->
+* [Configure Microsoft Edge policy settings on Windows devices](/deployedge/configure-microsoft-edge)<!-- bucket 5 top -->
+* [Microsoft Edge - Policies](/deployedge/microsoft-edge-policies)<!-- bucket 9 top -->
+* [Microsoft Edge - Update policies](/deployedge/microsoft-edge-update-policies)<!-- bucket 9 -->
+   * [Update](/deployedge/microsoft-edge-update-policies#update)
+   * [UpdatesSuppressed](/deployedge/microsoft-edge-update-policies#updatessuppressed)
+   * [Update (WebView)](/deployedge/microsoft-edge-update-policies#update-webview)
+* [Microsoft Edge WebView2 - Policies](/deployedge/microsoft-edge-webview-policies)<!-- bucket 9 bottom -->
+
+Modern Lifecycle Policy documentation:
+* [Modern Lifecycle Policy](/lifecycle/policies/modern)
+
+App management documentation:
+* [Update Microsoft Edge](/intune/configmgr/apps/deploy-use/deploy-edge#update-microsoft-edge) in _Microsoft Edge Management_.
+
+Windows Server Management documentation:
+* [Windows Server Update Services (WSUS) overview](/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus)<!-- todo: deprecated -->
+
+GitHub:
+* [WebView2Feedback](https://github.com/MicrosoftEdge/WebViewFeedback) repo.