diff --git a/microsoft-edge/devtools/whats-new/index.md b/microsoft-edge/devtools/whats-new/index.md
index 88182e54cf..19ed075b27 100644
--- a/microsoft-edge/devtools/whats-new/index.md
+++ b/microsoft-edge/devtools/whats-new/index.md
@@ -14,6 +14,22 @@ To check out the latest features of Microsoft Edge DevTools and the Microsoft Ed
 
 What's new articles correspond to historical releases of Microsoft Edge, and are not updated over time.  References to "new features" and "experiments" might become outdated as new versions of Microsoft Edge are released.
 
+<!-- maint:
+toc.yml - add new what's new page, move a what's new page to archive
+/devtools/whats-new/index.md - add new what's new page, remove earliest what's new page -->
+* [What's new in DevTools (Microsoft Edge 149)](./149.md)
+* [What's new in DevTools (Microsoft Edge 148)](./148.md)
+* [What's new in DevTools (Microsoft Edge 147)](./147.md)
+* [What's new in DevTools (Microsoft Edge 146)](./146.md)
+* [What's new in DevTools (Microsoft Edge 145)](./145.md)
+* [What's new in DevTools (Microsoft Edge 144)](./144.md)
+* [What's new in DevTools (Microsoft Edge 143)](./143.md)
+* [What's new in DevTools (Microsoft Edge 142)](./2025/10/devtools-142.md)
+* [What's new in DevTools (Microsoft Edge 141)](./2025/10/devtools-141.md)
+* [What's new in DevTools (Microsoft Edge 140)](./2025/09/devtools-140.md)
+
+For earlier What's new pages, see **Archive** in the table of contents.
+
 
 <!-- ====================================================================== -->
 ## Download the preview channels
diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml
index fcad6aaead..efa4cfbf06 100644
--- a/microsoft-edge/toc.yml
+++ b/microsoft-edge/toc.yml
@@ -30,6 +30,14 @@
           href: ./web-platform/release-notes/index.md
           displayName: what's new, announcements
 
+          # latest 10
+          # maint:
+          # toc.yml - add new relnotes page, move a relnotes page to archive
+          # /web-platform/release-notes/index.md - add new relnotes page, remove earliest relnotes page
+        - name: Microsoft Edge 151
+          href: ./web-platform/release-notes/151.md
+          displayName: Microsoft Edge 151 web platform release notes (Aug. 2026)  # page title
+
         - name: Microsoft Edge 150
           href: ./web-platform/release-notes/150.md
           displayName: Microsoft Edge 150 web platform release notes (Jul. 2026)  # page title
@@ -65,13 +73,13 @@
         - name: Microsoft Edge 142
           href: ./web-platform/release-notes/142.md
           displayName: Microsoft Edge 142 web platform release notes (Oct. 2025)  # page title
-
-        - name: Microsoft Edge 141
-          href: ./web-platform/release-notes/141.md
-          displayName: Microsoft Edge 141 web platform release notes (Oct. 2025)  # page title
         # keep 10 items above
         - name: Archive
           items:
+            - name: Microsoft Edge 141
+              href: ./web-platform/release-notes/141.md
+              displayName: Microsoft Edge 141 web platform release notes (Oct. 2025)  # page title
+
             - name: Microsoft Edge 140
               href: ./web-platform/release-notes/140.md
               displayName: Microsoft Edge 140 web platform release notes (Sep. 2025)  # page title
@@ -166,7 +174,11 @@
             - name: What's new in Microsoft Edge DevTools
               href: ./devtools/whats-new/index.md
               displayName: release notes, announcements
-# latest 10 What's new
+
+              # latest 10
+              # maint:
+              # toc.yml - add new what's new page, move a what's new page to archive
+              # /devtools/whats-new/index.md - add new what's new page, remove earliest what's new page
             - name: Microsoft Edge 149
               href: ./devtools/whats-new/149.md
               displayName: What's new in DevTools (Microsoft Edge 149)  # page title
diff --git a/microsoft-edge/web-platform/release-notes/147.md b/microsoft-edge/web-platform/release-notes/147.md
index 1d03a913c2..c529bd4e2f 100644
--- a/microsoft-edge/web-platform/release-notes/147.md
+++ b/microsoft-edge/web-platform/release-notes/147.md
@@ -49,7 +49,6 @@ To stay up-to-date and get the latest web platform features, download a preview
   * [Web Serial API on Android](#web-serial-api-on-android)
   * [WebXR Layers](#webxr-layers)
   * [WebXR Plane Detection](#webxr-plane-detection)
-  * [XML parsing in Rust for non-XSLT scenarios](#xml-parsing-in-rust-for-non-xslt-scenarios)
 * [Deprecated or removed features](#deprecated-or-removed-features)
   * [Remove inline XSLT for production of SVG](#remove-inline-xslt-for-production-of-svg)
 * [Origin trials](#origin-trials)
@@ -427,20 +426,6 @@ See also:
 * [WebXR Device API](https://developer.mozilla.org/docs/Web/API/WebXR_Device_API) at MDN.
 
 
-<!-- ------------------------------ -->
-#### XML parsing in Rust for non-XSLT scenarios
-
-Microsoft Edge now uses a Rust-based XML parser, in scenarios where XSLT processing isn't required.
-
-The Rust XML parser improves security by eliminating memory-corruption bugs in XML parsing.  This applies to:
-* The DOMParser Web API.
-* `responseXML` of `XMLHttpRequest`.
-* SVG documents.
-
-See also:
-* [DOMParser](https://developer.mozilla.org/docs/Web/API/DOMParser) at MDN.
-
-
 <!-- ====================================================================== -->
 ## Deprecated or removed features
 
diff --git a/microsoft-edge/web-platform/release-notes/150.md b/microsoft-edge/web-platform/release-notes/150.md
index f26658aed9..4437d1defe 100644
--- a/microsoft-edge/web-platform/release-notes/150.md
+++ b/microsoft-edge/web-platform/release-notes/150.md
@@ -28,7 +28,6 @@ To stay up-to-date and get the latest web platform features, download a preview
    * [Comma-separated container queries](#comma-separated-container-queries)
    * [Expose unprintable areas via CSS](#expose-unprintable-areas-via-css)
    * [Media element pseudo-classes](#media-element-pseudo-classes)
-   * [CSS `alpha()` function](#css-alpha-function)
    * [`named-feature()` function for CSS @supports](#named-feature-function-for-css-supports)
    * [`overscroll-behavior: chain`](#overscroll-behavior-chain)
    * [`flex-wrap:balance`](#flex-wrapbalance)
@@ -38,7 +37,6 @@ To stay up-to-date and get the latest web platform features, download a preview
    * [Updating all `<selectedcontent>` element in a customizable `<select>`](#updating-all-selectedcontent-element-in-a-customizable-select)
    * [Streaming out-of-order HTML](#streaming-out-of-order-html)
 * [Web APIs](#web-apis)
-   * [Expose the `FontFaceSet` interface globally](#expose-the-fontfaceset-interface-globally)
    * [Disable SVG filters on cross-origin iframes and plugins](#disable-svg-filters-on-cross-origin-iframes-and-plugins)
    * [`MediaStreamTrackProcessor` frame counters](#mediastreamtrackprocessor-frame-counters)
    * [Opaque origin for `data:` URLs](#opaque-origin-for-data-urls)
@@ -228,17 +226,6 @@ See also:
 * [`:volume-locked` CSS pseudo-class](https://developer.mozilla.org/docs/Web/CSS/Reference/Selectors/:volume-locked) at MDN.
 
 
-<!-- ------------------------------ -->
-#### CSS `alpha()` function
-
-The CSS `alpha()` function creates a new color by applying a specified alpha value to an existing color.
-
-For example, `alpha(from red / 0.5)` creates a semi-transparent red color with 50% opacity.
-
-See also:
-* [Relative Alpha Colors](https://drafts.csswg.org/css-color-5/#relative-alpha) in _CSS Color Module Level 5_.
-
-
 <!-- ------------------------------ -->
 #### `named-feature()` function for CSS `@supports`
 
@@ -357,17 +344,6 @@ See also:
 The following new Web API features are included in Microsoft Edge.
 
 
-<!-- ------------------------------ -->
-#### Expose the `FontFaceSet` interface globally
-
-Previously, the `FontFaceSet` interface was not exposed as a global property.  Chromium's interface definition language (IDL) for `FontFaceSet` previously incorrectly applied `LegacyNoInterfaceObject` to `FontFaceSet`, hiding it as a global property.
-
-This change aligns Chromium with the CSS Font Loading spec, and with Safari and Firefox.
-
-See also:
-* [FontFaceSet](https://developer.mozilla.org/docs/Web/API/FontFaceSet) at MDN.
-
-
 <!-- ------------------------------ -->
 #### Disable SVG filters on cross-origin iframes and plugins
 
diff --git a/microsoft-edge/web-platform/release-notes/151.md b/microsoft-edge/web-platform/release-notes/151.md
new file mode 100644
index 0000000000..427a9a7b1f
--- /dev/null
+++ b/microsoft-edge/web-platform/release-notes/151.md
@@ -0,0 +1,400 @@
+---
+title: Microsoft Edge 151 web platform release notes (Jul. 2026)
+description: Microsoft Edge 151 web platform release notes (Jul. 2026)
+author: MSEdgeTeam
+ms.author: msedgedevrel
+ms.topic: article
+ms.service: microsoft-edge
+ms.date: 07/30/2026
+---
+# Microsoft Edge 151 web platform release notes (Jul. 2026)
+
+The following are the new web platform features and updates in Microsoft Edge 151, which releases on Jul. 30, 2026.
+
+To stay up-to-date and get the latest web platform features, download a preview channel of Microsoft Edge (Beta, Dev, or Canary); go to [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider).
+
+**Detailed contents:**
+
+* [Microsoft Edge DevTools](#microsoft-edge-devtools)
+* [WebView2](#webview2)
+* [CSS features](#css-features)
+   * [CSS `ruby-overhang` property](#css-ruby-overhang-property)
+   * [Changed the `position-anchor` initial value to `normal`](#changed-the-position-anchor-initial-value-to-normal)
+   * [CSS `alpha()` function](#css-alpha-function)
+   * [`animation-trigger` actions no longer auto-rewind](#animation-trigger-actions-no-longer-auto-rewind)
+* [HTML features](#html-features)
+   * [`<usermedia>` element](#usermedia-element)
+   * [Reference target](#reference-target)
+   * [`aria-actions` attribute](#aria-actions-attribute)
+   * [`shadowrootslotassignment` attribute for declarative shadow DOM](#shadowrootslotassignment-attribute-for-declarative-shadow-dom)
+* [Web APIs](#web-apis)
+   * [Device event permission request API](#device-event-permission-request-api)
+   * [Duplicate successive navigations are ignored](#duplicate-successive-navigations-are-ignored)
+   * [Cross-origin redirect timing in the Navigation Timing API](#cross-origin-redirect-timing-in-the-navigation-timing-api)
+   * [LanguageDetector support for Traditional and Simplified Chinese](#languagedetector-support-for-traditional-and-simplified-chinese)
+   * [`soft-navigation` and `interaction-contentful-paint` performance entries](#soft-navigation-and-interaction-contentful-paint-performance-entries)
+   * [Exposed the `FontFaceSet` interface globally](#exposed-the-fontfaceset-interface-globally)
+   * [Speculation rules: `form_submission` field](#speculation-rules-form_submission-field)
+   * [Wheel event indicates whether a momentum scroll](#wheel-event-indicates-whether-a-momentum-scroll)
+   * [XML parsing in Rust for non-XSLT scenarios](#xml-parsing-in-rust-for-non-xslt-scenarios)
+   * [`textStream()` method for `Response`, `Request`, and `Body`](#textstream-method-for-response-request-and-body)
+* [Origin trials](#origin-trials)
+
+
+<!-- ====================================================================== -->
+## Microsoft Edge DevTools
+
+See [What's new in Microsoft Edge DevTools](../../devtools/whats-new/index.md).
+<!-- todo: when exists, use instead:
+See [What's new in DevTools (Microsoft Edge 151)](../../devtools/whats-new/151.md).
+-->
+
+
+<!-- ====================================================================== -->
+## WebView2
+
+See [Release notes for the WebView2 SDK](../../webview2/release-notes/index.md).
+<!-- todo: when exists, use instead:
+See [Release SDK 1.0.nnnn.nn, for Runtime nnn](../../webview2/release-notes/index.md#10nnnnnn) (Jul. 2026) in _Release notes for the WebView2 SDK_.
+-->
+
+
+<!-- ====================================================================== -->
+## CSS features
+
+The following new Cascading Style Sheets (CSS) features are included in Microsoft Edge.
+
+
+<!-- ------------------------------ -->
+#### CSS `ruby-overhang` property
+
+The `ruby-overhang` CSS property sets whether ruby annotations may overlap adjacent text.
+
+The property accepts the `auto`, `spaces` and `none` values, to control overhang of ruby annotation text.
+
+See also:
+* [`<ruby>` HTML ruby annotation element](https://developer.mozilla.org/docs/Web/HTML/Reference/Elements/ruby) at MDN.
+* [`ruby-overhang` CSS property](https://developer.mozilla.org/docs/Web/CSS/Reference/Properties/ruby-overhang) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Changed the `position-anchor` initial value to `normal`
+
+The initial value for the `position-anchor` CSS property is now `normal`.  Previously, the initial value was `none`.
+
+This aligns Microsoft Edge with other browsers and with the anchor positioning specification.
+
+* If `position-area` is set to `none`, `normal` behaves like `none`.
+* If `position-area` is not set to `none`, `normal` behaves like `auto`.
+
+See also:
+* [`position-anchor` CSS property](https://developer.mozilla.org/docs/Web/CSS/Reference/Properties/position-anchor) at MDN.
+* [`position-area` CSS property](https://developer.mozilla.org/docs/Web/CSS/Reference/Properties/position-area) at MDN.
+
+
+<!-- ------------------------------ -->
+#### CSS `alpha()` function
+
+The CSS `alpha()` function creates a new color by applying a specified alpha value to an existing color.
+
+For example, `alpha(from red / 0.5)` creates a semi-transparent red color with 50% opacity.
+
+See also:
+* [Relative Alpha Colors](https://drafts.csswg.org/css-color-5/#relative-alpha) in _CSS Color Module Level 5_.
+
+
+<!-- ------------------------------ -->
+#### `animation-trigger` actions no longer auto-rewind
+
+The values `play`, `play-forwards` and `play-backwards` of the `animation-trigger` CSS property instruct the animation trigger to play the animation.
+
+These values don't automatically rewind the animation anymore: when the animation has already run to completion and `play`, `play-forwards` or `play-backwards` is used, the animation will not restart.
+
+See also:
+* [CSS scroll-triggered animations are coming!](https://developer.chrome.com/blog/scroll-triggered-animations)
+
+
+<!-- ====================================================================== -->
+## HTML features
+
+The following new HTML features are included in Microsoft Edge.
+
+
+<!-- ------------------------------ -->
+#### `<usermedia>` element
+
+The `<usermedia>` HTML element is a browser-provided button that, upon activation, toggles camera or microphone streams.  If required, the button prompts the user to choose whether to grant the page access to the camera and microphone.
+
+This browser-provided button enables a better user experience, because the permission prompt is directly linked to the user intent.
+
+The `<usermedia>` element was previously available as an origin trial under the more generic `<permission>` element.  Based on feedback from developers and other browser vendors, the `<permission>` element has been renamed to the specific `<usermedia>` element, to provide a more tailored and powerful developer experience.
+
+See also:
+* [`<usermedia>` element](https://github.com/WICG/PEPC/blob/main/usermedia_element.md), in the "WICG / PEPC" repo.
+
+
+<!-- ------------------------------ -->
+#### Reference target
+
+The `referenceTarget` property of a `ShadowRoot` object forwards attributes such as `for`, `aria-labelledby`, `popovertarget`, and `commandfor` to elements inside a shadow DOM.  You can use this to, for example, link a `<label>` to its `<input>`, even if the `<input>` is in the shadow DOM of a web component.
+
+When a shadow host specifies an element in its shadow tree to act as its reference target, all ID references that point to the shadow host are forwarded to the reference target element instead.
+
+A reference target can also be set in HTML, by using the `shadowrootreferencetarget` attribute, like in the following example:
+
+```html
+<label for="my-checkbox">Checkbox value</label>
+<custom-checkbox id="my-checkbox">
+  <template shadowrootmode="open" shadowrootreferencetarget="real-checkbox">
+    <input id="real-checkbox" type="checkbox">
+  </template>
+</custom-checkbox>
+```
+
+See also:
+* [`referencetarget`](https://developer.mozilla.org/docs/Web/API/Element/attachShadow#referencetarget), in _Element: `attachShadow()` method_, at MDN.
+* [`Shadowroot.referencetarget`](https://developer.mozilla.org/docs/Web/API/ShadowRoot#shadowroot.referencetarget), in _`ShadowRoot`_, at MDN.
+* [`shadowrootreferencetarget`](https://developer.mozilla.org/docs/Web/HTML/Reference/Elements/template#shadowrootreferencetarget), in _`<template>` HTML content template element_, at MDN.
+
+
+<!-- ------------------------------ -->
+#### `aria-actions` attribute
+
+The `aria-actions` HTML attribute exposes secondary actions for composite interactive widgets.
+
+For example, you can use the `aria-actions` attribute to expose the close button of a tab, which is a secondary action for the tab widget, as follows:
+
+```html
+<div class="tab" aria-actions="close-tab">
+  Tab title
+  <button id="close-tab">Close</button>
+</div>
+```
+
+Secondary actions placed within composite interactive widgets is a common UI pattern.  The `aria-actions` attribute allows you to expose these secondary action buttons directly, to improve discoverability for assistive technology (AT) users.
+
+See also:
+* [Feature: `aria-actions`](https://chromestatus.com/feature/5161589307867136) at Chrome Platform Status.
+
+
+<!-- ------------------------------ -->
+#### `shadowrootslotassignment` attribute for declarative shadow DOM
+
+The `shadowrootslotassignment` attribute of the `<template>` element allows declarative shadow roots to use manual slot assignment.
+
+Previously, manual slot assignment was only available via JavaScript, as follows:
+
+```javascript
+attachShadow({slotAssignment: "manual"})
+```
+
+You can now declare manual slot assignment via HTML, as follows:
+
+```html
+<template shadowrootslotassignment="manual">
+</template>
+```
+
+See also:
+* [ShadowRoot: slotAssignment property](https://developer.mozilla.org/docs/Web/API/ShadowRoot/slotAssignment) at MDN.
+
+
+<!-- ---------------------------------------------------------------------- -->
+## Web APIs
+
+The following new Web API features are included in Microsoft Edge.
+
+
+<!-- ------------------------------ -->
+#### Device event permission request API
+
+You can call `DeviceMotionEvent.requestPermission()` and `DeviceOrientationEvent.requestPermission()` to ask the browser for device motion and orientation data to be shared with the webpage.
+
+These methods return a promise that resolves to either `granted` or `denied`, based on whether the user has allowed the user agent to share sensor data with the page.
+
+See also:
+* [DeviceMotionEvent: requestPermission() static method](https://developer.mozilla.org/docs/Web/API/DeviceMotionEvent/requestPermission_static) at MDN.
+* [DeviceOrientationEvent: requestPermission() static method](https://developer.mozilla.org/docs/Web/API/DeviceOrientationEvent/requestPermission_static) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Duplicate successive navigations are ignored
+
+When a navigation is already in progress, Microsoft Edge now ignores a new navigation request to the same URL as the previous navigation request.
+
+Duplicate navigations in quick succession are often caused by an accidental double-click.  Duplicate navigations can waste resources by canceling the ongoing navigation and starting a new navigation.  This optimization improves performance and improves the user experience.
+
+See also:
+* [Experiment with keeping older navigation on duplicate navigation](https://issues.chromium.org/issues/366060351) in the Chromium bug tracker.
+
+
+<!-- ------------------------------ -->
+#### Cross-origin redirect timing in the Navigation Timing API
+
+The `Timing-Allow-Origin` header, when used in chains of cross-origin redirects, provides values for `redirectCount`, `redirectStart` and `redirectEnd` to the destination document, via the Navigation Timing API.
+
+This lets you measure and optimize your cross-origin redirects.
+
+See also:
+* [Navigation timing](https://developer.mozilla.org/docs/Web/API/Performance_API/Navigation_timing) at MDN.
+* [Timing-Allow-Origin header](https://developer.mozilla.org/docs/Web/HTTP/Reference/Headers/Timing-Allow-Origin) at MDN.
+
+
+<!-- ------------------------------ -->
+#### LanguageDetector support for Traditional and Simplified Chinese
+
+The LanguageDetector API can now detect and differentiate text that's written in Traditional Chinese or Simplified Chinese.
+
+The LanguageDetector API returns the language code `zh-Hant` for Traditional Chinese, and `zh-Hans` for Simplified Chinese.  Previously, the LanguageDetector API returned `zh` for both Traditional Chinese and Simplified Chinese.
+
+See also:
+* [Detect languages with the Language Detector API](../languagedetector-api.md)
+* [LanguageDetector API](https://microsoftedge.github.io/Demos/built-in-ai/playgrounds/languagedetector-api/)
+
+
+<!-- ------------------------------ -->
+#### `soft-navigation` and `interaction-contentful-paint` performance entries
+
+The Performance API now includes two new `PerformanceEntry` types:
+
+* `soft-navigation` - Reports same-document history-state changes that are initiated by interactions.
+* `interaction-contentful-paint` - Reports new contentful paints within parts of the page that were modified by a user interaction.  This helps you understand interaction loading latency.
+
+Use these new entries to measure the performance of soft navigations.  A _soft navigation_ is a JavaScript-driven navigation in a Single Page App (SPA).
+
+See also:
+* [PerformanceEntry](https://developer.mozilla.org/docs/Web/API/PerformanceEntry) at MDN.
+* [Performance APIs](https://developer.mozilla.org/docs/Web/API/Performance_API) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Exposed the `FontFaceSet` interface globally
+
+The `FontFaceSet` interface is now exposed globally.
+
+Previously, the `FontFaceSet` interface was not exposed as a global property.
+
+This change aligns Microsoft Edge with the CSS Font Loading spec, and with Safari and Firefox.
+
+See also:
+* [FontFaceSet](https://developer.mozilla.org/docs/Web/API/FontFaceSet) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Speculation rules: `form_submission` field
+
+You can now set the `"form_submission": true` field on a prerender rule in the Speculation Rules API, to allow the prerender to be activated by a form submission navigation.
+
+Previously, form submissions could never activate a prerendered page.  Now, setting `"form_submission": true` tells the browser to prepare the prerender, so that when the user submits a form whose result URL matches the prerendered URL, the prerender activates immediately.
+
+This is useful for search forms where the result URL can be predicted in advance.  For example, to prerender the result of a search form that navigates to `/search?q=foo`, use the following speculation rules:
+
+```html
+<script type="speculationrules">
+{
+  "prerender": [
+    {
+      "urls": ["/search?q=foo"],
+      "form_submission": true
+    }
+  ]
+}
+</script>
+```
+
+See also:
+* [Speculation Rules API](https://developer.mozilla.org/docs/Web/API/Speculation_Rules_API) at MDN.
+
+
+<!-- todo: when support is added in edge, uncomment section and move to correct relnotes page -->
+<!-- ------------------------------ 
+#### Support for unspoken punctuation in the Web Speech API
+
+The `SpeechRecognition` interface of the Web Speech API now has an `unspokenPunctuation` boolean attribute.
+
+When set to `true`, the `unspokenPunctuation` attribute directs the speech-recognition engine to automatically infer and insert punctuation marks (such as periods, commas, and question marks) based on the user's pauses, grammatical structure, and intonation, without requiring explicit spoken punctuation commands.
+
+See also:
+* [Convert speech to text with the SpeechRecognition API](../speech-recognition-api.md)
+-->
+
+
+<!-- ------------------------------ -->
+#### Wheel event indicates whether a momentum scroll
+
+The `WheelEvent` interface now includes a `momentum` attribute, which indicates whether the event is part of a momentum scroll.
+
+The `momentum` attribute is useful, for example, on a device that has a trackpad, where the user can perform a fling gesture to scroll content.  Many devices continue to fire wheel events for a while after trackpad motion stops, to simulate scrolling inertia.  The `momentum` attribute differentiates those simulated events from the events that are fired during the physical trackpad interaction.
+
+See also:
+* [WheelEvent](https://developer.mozilla.org/docs/Web/API/WheelEvent) at MDN.
+
+
+<!-- ------------------------------ -->
+#### XML parsing in Rust for non-XSLT scenarios
+
+Microsoft Edge now uses a Rust-based XML parser, in scenarios where XSLT processing isn't required.
+
+The Rust XML parser improves security by eliminating memory-corruption bugs in XML parsing.  This applies to:
+* The DOMParser Web API.
+* The `responseXML` property on an `XMLHttpRequest` (XHR) object.
+* SVG documents.
+
+See also:
+* [DOMParser](https://developer.mozilla.org/docs/Web/API/DOMParser) at MDN.
+
+
+<!-- ------------------------------ -->
+#### `textStream()` method for `Response`, `Request`, and `Body`
+
+The `Request`, `Response`, and `Blob` interfaces now include a `textStream()` method.
+
+The `textStream()` method provides a direct way to read text from a byte stream, without requiring first piping the stream through a `TextDecoderStream()`.
+
+See also:
+* [Request](https://developer.mozilla.org/docs/Web/API/Request) at MDN.
+* [Response](https://developer.mozilla.org/docs/Web/API/Response) at MDN.
+* [Blob](https://developer.mozilla.org/docs/Web/API/Blob) at MDN.
+* [TextDecoderStream](https://developer.mozilla.org/docs/Web/API/TextDecoderStream) at MDN.
+
+
+<!-- ====================================================================== -->
+## Origin trials
+
+The following are origin trials for new experimental APIs that are available in Microsoft Edge.
+
+Origin trials let you try experimental APIs on your own live website for a limited time.  To learn more about origin trials, see [Use origin trials in Microsoft Edge](../../origin-trials/index.md).
+
+For the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
+
+| Name | Description | Register |
+|---|---|---|
+| Soft navigation heuristics | Exposes soft-navigation heuristics for collecting performance metrics in single-page apps. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/ec952482-49f0-4980-a451-13ea3f9a7220) |
+| URL and eval hashes in CSP script-src | Introduces url- and eval- hashes for `script-src` CSP directives, replacing hostname-based allowlists and `unsafe-eval`. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/6bd50a0d-6f30-425f-beba-034be41bb013) |
+| Web Install API | Allows a website to install another website as a web app by using `navigator.install()`. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/bcf7d28f-6bdf-45d8-9207-63c97a042407) |
+| `OpaqueRange` | Enables creating live ranges over text inside `<input>` and `<textarea>` elements that automatically update as the user edits.  These ranges support geometry methods such as `getBoundingClientRect()` and the CSS Custom Highlight API, which enables use cases such as caret-positioned popups and inline spell-check highlighting directly on form controls, without cloning elements or exposing internal DOM structure. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/5f4620e8-2969-4579-a5c6-304b8fae7200) |
+| Digital Credentials API - Issuance Support | Triggers issuance of user credentials from a credential issuer server to a digital wallet application. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/89fbbd25-ce49-43b6-a206-dd0909394ed8) |
+| `prerender_until_script` Speculation Rules API action | A Speculation Rules API action that prerenders a page but switches to prefetching when a script executes. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/b7fcdb4e-b3ab-4bbe-ba5a-0d4e655ad690) |
+| CPU Performance API | Exposes information about the user's device capabilities, for use with the Compute Pressure API. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/505dbb22-2d7f-4c91-9a2b-3913345a956e) |
+| Connection allowlists | Restricts connections from a document or worker to a server-distributed allowlist of endpoints. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/a20a4374-39fd-445f-9348-f6c8737a45de) |
+| `focus-without-user-activation` permissions policy | Gives an embedder control over programmatic focus from embedded content via the `focus-without-user-activation` permissions policy.  When the policy is denied for a frame, programmatic focus calls (`element.focus()`, `autofocus`, `window.focus()`, `dialog.showModal()`, and popover focusing) are blocked unless triggered by user activation, or focus is being delegated. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/e5a1d64f-b04b-453f-9550-6d12c1f6bc99) |
+| Enhanced Canvas TextMetrics | Expands the TextMetrics Canvas API with selection rectangles, bounding-box queries, and glyph-cluster operations. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/c4ab8844-e904-46c1-94b6-7e2b5c19bf3e) |
+| WebAudio Configurable Render Quantum | Lets you specify a custom render quantum size when creating an `AudioContext` or `OfflineAudioContext`. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/d5574838-d416-4242-81a8-7833c107b028) |
+| Prerendering cross-origin iframes | Prerenders cross-origin iframes via an opt-in response header, instead of delaying them until page activation. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/46c24517-496a-4a6b-a4d3-604b08620d43) |
+| Container Timing | Monitors when an annotated DOM container is displayed and has finished its initial paint. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/79fd2cd8-2283-4ed8-a472-4a8281a73d86) |
+| Separate style and layout durations in the Long Animation Frame API | Adds `styleDuration`, `forcedStyleDuration`, `layoutDuration`, and `forcedLayoutDuration` properties for deeper CSS performance analysis. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/349e23d8-799a-4ac2-b45a-ffb91e09b4ce) |
+| Prompt API sampling parameters | The `topK` and `temperature` sampling parameters let you optimize model behavior per language model session. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/32d0cd0f-611d-411e-b48e-cfd8edfdbf73) |
+| `<install>` HTML element | Declaratively install other websites as web apps by using the `<install>` element. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/b2eb5c7f-7df0-4ad9-950e-2fbd2ebc08ec) |
+| Declarative CSS Module Scripts | Shares declarative stylesheets with shadow roots, including declarative shadow roots, using inline style modules. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/966b04dd-3da4-43f4-a6a0-66a785f129f4) |
+| HTML in canvas | Enables rendering HTML in canvas with new drawing methods and the `paint` event. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/a297467e-0030-4c4c-8739-48e130026c03) |
+| Gamepad raw input event | Instead of relying on frequent polling via `navigator.getGamepads()`, web pages can listen for `gamepadrawinputchanged` events.  These events are fired whenever changes are detected between input frames from the same device. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/4ecdb530-835b-447d-b27e-0b3be8e0412b) |
+| Autofill Event | Detects when browser autofill updates form controls, for adapting custom UI and validation. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/43534059-5696-4eaf-8bbd-eba4c4f86e88) |
+| WebAssembly Custom Descriptors V2 | Stores data associated with source-level types more efficiently, in custom descriptor objects. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/9c75e7f3-49cb-43de-9745-7458ff9c3689) |
+| Speculative Load measurement | `performance.speculations` exposes data about used and unused preloads, prefetches, and prerenders.  This helps you measure the effectiveness of speculative loading strategies and optimize performance-versus-cost tradeoffs. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/246de200-45d2-4f44-8047-001d385c90c5) |
+| WebMCP | Enables your site to register tools for an in-browser agent to complete tasks on behalf of a user. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/0b76fe60-b266-458e-a285-04e375c0c31a) |
+| Email Verification Protocol | Enables websites to verify email ownership by using cryptographic tokens that are issued by email providers.  This reduces reliance on email one-time passcodes (OTPs), and streamlines sign-up, sign-in, and recovery flows. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/683027d2-a798-460f-9b35-03a95002d9af) |
+
+
+<!-- ====================================================================== -->
+> [!NOTE]
+> Portions of this page are modifications based on work created and shared by Chromium.org and used according to terms described in the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0).
diff --git a/microsoft-edge/web-platform/release-notes/index.md b/microsoft-edge/web-platform/release-notes/index.md
index 6880f2a65b..f55c8bc058 100644
--- a/microsoft-edge/web-platform/release-notes/index.md
+++ b/microsoft-edge/web-platform/release-notes/index.md
@@ -13,6 +13,22 @@ These release notes cover the new web platform features and updates in Microsoft
 
 To stay up-to-date and get the latest web platform features, download a preview channel of Microsoft Edge (Beta, Dev, or Canary); go to [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider).
 
+<!-- maint:
+toc.yml - add new relnotes page, move a relnotes page to archive
+/web-platform/release-notes/index.md - add new relnotes page, remove earliest relnotes page -->
+* [Microsoft Edge 151 web platform release notes (Jul. 2026)](./151.md)
+* [Microsoft Edge 150 web platform release notes (Jul. 2026)](./150.md)
+* [Microsoft Edge 149 web platform release notes (Jun. 2026)](./149.md)
+* [Microsoft Edge 148 web platform release notes (May 2026)](./148.md)
+* [Microsoft Edge 147 web platform release notes (Apr. 2026)](./147.md)
+* [Microsoft Edge 146 web platform release notes (Mar. 2026)](./146.md)
+* [Microsoft Edge 145 web platform release notes (Feb. 2026)](./145.md)
+* [Microsoft Edge 144 web platform release notes (Jan. 2026)](./144.md)
+* [Microsoft Edge 143 web platform release notes (Dec. 2025)](./143.md)
+* [Microsoft Edge 142 web platform release notes (Oct. 2025)](./142.md)
+
+For earlier release notes, see **Archive** in the table of contents.
+
 
 <!-- ====================================================================== -->
 ## See also
diff --git a/microsoft-edge/webview2/concepts/user-data-folder.md b/microsoft-edge/webview2/concepts/user-data-folder.md
index b97d4cc29c..671bdd745f 100644
--- a/microsoft-edge/webview2/concepts/user-data-folder.md
+++ b/microsoft-edge/webview2/concepts/user-data-folder.md
@@ -6,15 +6,15 @@ ms.author: msedgedevrel
 ms.topic: article
 ms.service: microsoft-edge
 ms.subservice: webview
-ms.date: 11/14/2025
+ms.date: 06/26/2026
 ---
 # Manage user data folders
-<!-- # old title: Manage the user data folder -->
 
 The user data folder (UDF) is a folder stored on the user's machine, that contains data related to the host app and WebView2.  WebView2 apps use user data folders to store browser data, such as cookies, permissions, and cached resources.
 
 
-**Terminology:**
+<!-- ====================================================================== -->
+## Terminology
 
 | Term | Definition |
 |---|---|
@@ -29,8 +29,8 @@ WebView2 creates the UDF in the default location for the platform, or in the cus
 By default, WebView2 creates a UDF in the default location for the particular platform.  This works well on some platforms, but not others.  If your app has specific needs, you can specify a custom UDF location.
 
 
-<!-- ------------------------------ -->
-#### Suitable custom UDF locations
+<!-- ====================================================================== -->
+## Suitable custom UDF locations
 
 If you specify a custom UDF location, it should meet the following requirements:
 
@@ -47,15 +47,15 @@ WebView2 apps use user data folders (UDFs) to store browser data, such as cookie
 | Type of data | Description |
 |---|---|
 | `AllDomStorage` | DOM storage data, now and future. This browsing data kind is inclusive of `FileSystems`, `IndexedDb`, `WebSql`, `CacheStorage`. |
-| `AllProfile` | Profile data that should be wiped to make it look like a new profile. This does not delete account-scoped data like passwords but will remove access to account-scoped data by signing the user out.  All profile data, now and future. New profile data types may be added to this data kind in the future. This browsing data kind includes the data kinds `AllSite`, `DiskCache`, `DownloadHistory`, `GeneralAutofill`, `PasswordAutosave`, `BrowsingHistory`, and `Settings`. |
-| `AllSite` | All site data, now and future. This browsing data kind includes the data kinds `AllDomStorage` and `Cookies`. New site data types may be added to this data kind in the future. |
+| `AllProfile` | All profile data, now and future.  This is profile data that should be wiped to make it look like a new profile.  This doesn't delete account-scoped data, such as passwords, but removes access to account-scoped data by signing the user out.  This browsing data kind includes the data kinds `AllSite`, `DiskCache`, `DownloadHistory`, `GeneralAutofill`, `PasswordAutosave`, `BrowsingHistory`, and `Settings`. |
+| `AllSite` | All site data, now and future.  This browsing data kind includes the data kinds `AllDomStorage` and `Cookies`. |
 | `BrowsingHistory` | Browsing history data. |
 | `CacheStorage` | Data stored by the CacheStorage DOM API. |
 | `Cookies` | HTTP cookies data. |
 | `DiskCache` | Disk cache. |
 | `DownloadHistory` | Download history data. |
 | `FileSystems` | File systems data. |
-| `GeneralAutofill` | General autofill form data. This excludes password information and includes information such as names, street and email addresses, phone numbers, and arbitrary input. Includes payment data. |
+| `GeneralAutofill` | General autofill form data.  This excludes password information, and includes information such as names, street and email addresses, phone numbers, arbitrary input, and payment data. |
 | `IndexedDb` | Data stored by the IndexedDB DOM feature. |
 | `LocalStorage` | Data stored by the localStorage DOM API. |
 | `PasswordAutosave` | Password autosave data. |
@@ -85,6 +85,7 @@ Each instance of a WebView2 control is associated with a WebView2 session.
 
 A WebView2 control shares its WebView2 session with any other WebView2 control that uses the same UDF. This is true whether the WebView2 controls are in the same host app or different host apps. However, a UDF may only be shared among host apps that are in the same logon session (more specifically, only one HDESKTOP). See [Process model for WebView2 apps](../concepts/process-model.md).
 
+
 <!-- ====================================================================== -->
 ## How to move the UDF
 
@@ -102,103 +103,64 @@ To move a user data folder (UDF):
 
 The default user data folder (UDF) location varies per platform.
 
-
-<!-- ====================================================================== -->
-<!-- default UDF location -->
-
 ##### [Win32](#tab/win32)
 
-<!--
-**What is the default UDF location?**
--->
 On this platform, the default UDF location is the directory that the app executable (`.exe`) is running in.  The default UDF is the executable (`exe`) path of your app + `.WebView2`.  The file name of the UDF is the executable (`exe`) path of your app + `.WebView2`.
 
 For example, if you ran `D:\WebView2App\WebView2.exe`, a UDF folder would be created: `D:\WebView2App\WebView2.exe.WebView2\`.  As another example: `WebView2APISample.exe.WebView2\`.
 
-
 **Should you use default or custom UDF location?**
 
-In most cases, you should specify a custom UDF location, rather than using the default UDF location.  This ensures that the WebView2 control has Write access so that the WebView2 control is able to create the UDF and then write to it.  See the section "Specifying a custom UDF location" below.
-
+In most cases, you should specify a custom UDF location, rather than using the default UDF location.  This ensures that the WebView2 control has Write access so that the WebView2 control is able to create the UDF and then write to it.  See [Specifying a custom UDF location](#specifying-a-custom-udf-location), below.
 
 **Packaging:**
 
 Win32 MSIX packaging is a standalone `.exe`.
 
-
-<!-- ====================================================================== -->
-<!-- default UDF location -->
-
 ##### [.NET (WPF/WinForms)](#tab/dotnet)
 
-<!--
-**What is the default UDF location?**
--->
 On this platform, the default UDF location is the directory that the app executable (`.exe`) is running in.  The default UDF is the executable (`exe`) path of your app + `.WebView2`.  The file name of the UDF is the executable (`exe`) path of your app + `.WebView2`.
 
 For example, if you ran `D:\WebView2App\WebView2.exe`, a UDF folder would be created: `D:\WebView2App\WebView2.exe.WebView2\`.  As another example: `WebView2APISample.exe.WebView2\`.
 
-
 **Should you use default or custom UDF location?**
 
-In most cases, you should specify a custom UDF location, rather than using the default UDF location.  This ensures that the WebView2 control has Write access so that the WebView2 control is able to create the UDF and then write to it.  See the section "Specifying a custom UDF location" below.
-
-
-
-<!-- ====================================================================== -->
-<!-- default UDF location -->
+In most cases, you should specify a custom UDF location, rather than using the default UDF location.  This ensures that the WebView2 control has Write access so that the WebView2 control is able to create the UDF and then write to it.  See [Specifying a custom UDF location](#specifying-a-custom-udf-location), below.
 
 ##### [ClickOnce](#tab/clickonce)
 
-<!--
-**What is the default UDF location?**
--->
 On this platform, the default UDF location is the directory that the app executable (`.exe`) is running in (or a subdirectory of it).
 
-
 **Should you use default or custom UDF location?**
 
 In most cases, you should use the default UDF location.  The default location where the UDF will be created will have appropriate permissions at runtime; the default UDF location is a writeable location.
 
-
 **Why the default location is writeable:**
 
 At run time, ClickOnce automatically installs your host app in a location that WebView2 has Write permission for.  ClickOnce can use the default UDF location and guarantee that WebView2 has Write permissions to be able to create the UDF there.
 
-However, your host app might not be able to use that location to write data to.  If your host app can't write to the default UDF location, see the section "Specifying a custom UDF location" below.
-
+However, your host app might not be able to use that location to write data to.  If your host app can't write to the default UDF location, see [Specifying a custom UDF location](#specifying-a-custom-udf-location), below.
 
 **Cleanup:**
 
 At the end of the session, ClickOnce automatically cleans up.  
 
-
 **Packaging:**
 
 ClickOnce is a deployment method for lightweight transient apps; it's a hybrid model.  It's possible to persist a ClickOnce app, but that's not standard, typical practice.  
 
-
 **What type of platform app a ClickOnce app wraps:**
 
 A ClickOnce app usually contains a .NET app.
 
-
-<!-- ====================================================================== -->
-<!-- default UDF location -->
-
 ##### [WinUI 2 (UWP)](#tab/uwp)
 
-<!--
-**What is the default UDF location?**
--->
 On this platform, the default UDF location is the `ApplicationData\LocalFolder` subfolder in the package's folder.
 
-
 **Should you use default or custom UDF location?**
 
 On this platform, use the default UDF location.
 
-
 **Why the default location is writeable:**
 
 WinUI 2 (UWP) is a packaged platform; it runs in the sandbox and is packaged to run in the sandbox, not usually as separate files, but as an app bundle.
@@ -211,29 +173,19 @@ At run time, during the session only, your WebView2 host app is given access to
 
 WebView2 checks for that runtime, and creates the UDF in that writeable location.
 
-
 **Packaging:**
 
 A WinUI 2 (UWP) app is self-contained regarding dependencies and for deployment (DLLs), although it's not packaged into a single file.
 
 A WinUI 2 (UWP) app is per-user, and has Write access under the installed location.
 
-
-<!-- ====================================================================== -->
-<!-- default UDF location -->
-
 ##### [WinUI 3](#tab/winui3)
 
-<!--
-**What is the default UDF location?**
--->
 On this platform, the default UDF location is the `ApplicationData\LocalFolder` subfolder in the package's folder.
 
-
 **Should you use default or custom UDF location?**
 
-On this platform, use the default UDF location.
-
+On this platform, use the default UDF location if distributing as packaged.  If distributing as unpackaged, in scenarios where the install directory is protected, you must specify a custom UDF location.
 
 **Packaging:**
 
@@ -241,33 +193,22 @@ WinUI 3 is a "packaged" platform; it runs in the sandbox and is packaged to run
 
 ---
 
-<!-- end of "default location" tab-set -->
-
 
 <!-- ====================================================================== -->
 ## Specifying a custom UDF location
 
 How to specify a custom user data folder (UDF) location varies per platform.
 
-
-<!-- ====================================================================== -->
-<!-- custom UDF location -->
-
 ##### [Win32](#tab/win32)
 
-<!--
-**Should you use default or custom UDF location?**
--->
 On this platform, in most cases, you should specify a custom UDF location, rather than using the default UDF location.  This ensures that the WebView2 control has Write access so that the WebView2 control is able to create the UDF and then write to it.
 
 You should specify the same folder where all other app data is stored.
 
-
 **How to specify a custom UDF location:**
 
 Use [ICoreWebView2Environment](/microsoft-edge/webview2/reference/win32/icorewebview2environment) and the `userDataFolder` parameter.  But use the code below, which is from the `WebView2Samples` repo.<!-- this api ref contains incorrect content but use the code listing below -->
 
-
 **Example code:**
 
 ```cpp
@@ -284,39 +225,27 @@ HRESULT hr = CreateCoreWebView2EnvironmentWithOptions(
 
 For example code, see the Win32-appropriate, `.cpp` or `.cs` file, near [WebView2Samples repo > WebView2APISample](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/WebView2APISample).
 
-
 <!-- neither specific to custom nor default -->
 **Where browser data gets stored within the UDF:**
 
 After creation of the session and UDF, browser data from your WebView2 control is stored in a subfolder of `userDataFolder`.
 
-
 **Why you should use a custom UDF location on this platform:**
 
 If you don't specify a custom UDF location, the default location can produce a run-time failure, if using installer technologies, because installer technologies put the app and thus the UDF in a protected area of the filesystem, where WebView2 isn't able to create the UDF, and thus UDF creation will usually fail.  WebView2 will throw an error to let your host app know that the UDF can't be created at that location.
 
 If the host app is running from a location that the user doesn't have Write access to, WebView2 isn't able to create the UDF, and you will receive a runtime error during WebView2 startup.
 
-
-
-<!-- ====================================================================== -->
-<!-- custom UDF location -->
-
 ##### [.NET (WPF/WinForms)](#tab/dotnet)
 
-<!--
-**Should you use default or custom UDF location?**
--->
 On this platform, in most cases, you should specify a custom UDF location, rather than using the default UDF location.  This ensures that the WebView2 control has Write access so that the WebView2 control is able to create the UDF and then write to it.
 
-
 **How to specify a custom UDF location:**
 
 You should specify the same folder where all other app data is stored.
 
 Use the [CoreWebView2Environment.CreateAsync method](/dotnet/api/microsoft.web.webview2.core.corewebview2environment.createasync), passing a `userDataFolder` parameter.
 
-
 **Example code:**
 
 ```csharp
@@ -329,39 +258,28 @@ _task = CoreWebView2Environment.CreateAsync(BrowserExecutableFolder,
 
 For example code, see the .NET (WPF & WinForms)-appropriate, .cpp or .cs file, near [WebView2Samples repo > WebView2WpfBrowser](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/WebView2WpfBrowser).
 
-
 **Why you need to specify a custom UDF on this platform:**
 
 If you don't specify a custom UDF location, the default location can produce a run-time failure, if using installer technologies.  This is because installer technologies put the app and thus the UDF in a protected area of the filesystem, where WebView2 isn't able to create the UDF, and thus UDF creation will usually fail.
 
 WebView2 will throw an error to let your host app know that the UDF can't be created at that location.
 
-
 <!-- neither focused on default nor custom -->
 **Where data is stored within the UDF:**
 After creation of the session and UDF, browser data from your WebView2 control is stored in a subfolder of `userDataFolder`.
 
-
-<!-- ====================================================================== -->
-<!-- custom UDF location -->
-
 ##### [ClickOnce](#tab/clickonce)
 
-<!--
-**Should you use default or custom UDF location?**
--->
 On this platform, in most cases, you should use the default UDF location.
 
 If you specify a custom UDF location, make sure that user data folder location has appropriate Read/Write permissions for the WebView2 app runtime.
 
-
 **How to specify a custom UDF location:**
 
 Use the [CoreWebView2Environment.CreateAsync method](/dotnet/api/microsoft.web.webview2.core.corewebview2environment.createasync), passing a `userDataFolder` parameter.
 
 You should specify the same folder where all other app data is stored.
 
-
 **Example code:**
 
 ```csharp
@@ -374,60 +292,55 @@ _task = CoreWebView2Environment.CreateAsync(BrowserExecutableFolder,
 
 For example code, see the .NET (WPF & WinForms)-appropriate, .cpp or .cs file, near [WebView2Samples repo > WebView2WpfBrowser](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/WebView2WpfBrowser).
 
-
 <!-- neither specific to custom nor default -->
 **Where browser data gets stored within the UDF:**
 
 After creation of the session and UDF, browser data from your WebView2 control is stored in a subfolder of `userDataFolder`.
 
-
-<!-- ====================================================================== -->
-<!-- custom UDF location -->
-
 ##### [WinUI 2 (UWP)](#tab/uwp)
 
-<!--
-**Should you use default or custom UDF location?**
--->
 On this platform, use the default UDF location.
 
-
 **Where browser data gets stored within the UDF:**
 
 After creation of the session and UDF, browser data from your WebView2 control is stored in a subfolder of `userDataFolder`.
 
-
 **Example code:**
 
-For example code, see the WinUI 2 (UWP) `.cs` file, at [WebView2Samples repo > webview2_sample_uwp](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/webview2_sample_uwp).
-
-
-
-<!-- ====================================================================== -->
-<!-- custom UDF location -->
+For example code, see line 161 in [/webview2_sample_uwp/Pages/SettingsPage.xaml.cs](https://github.com/MicrosoftEdge/WebView2Samples/blob/main/SampleApps/webview2_sample_uwp/Pages/SettingsPage.xaml.cs#L161).  This sample app doesn't set a custom user data folder.  This code shows what the user data folder turned out to be.
 
 ##### [WinUI 3](#tab/winui3)
 
-<!--
-**Should you use default or custom UDF location?**
--->
-On this platform, use the default UDF location.
-
+On this platform, if distributing as unpackaged to a protected install directory, you must specify a custom UDF location.
 
 **Example code:**
 
-For example code, see the WinUI 3 `.cs` file, at [WebView2Samples repo > WebView2_WinUI3_Sample](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/GettingStartedGuides/WinUI3_GettingStarted).
-
+```csharp
+try {
+    // The default user data folder is next to the executable; however, the install
+    // dir (that is, /Program Files/) is protected.
+    var userDataFolder = Path.Combine(
+      Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData),
+      "YOURAPPNAME", "WebView2"); // You need to decide if you want to keep this 
+      // folder during uninstall, or add uninstall code that removes this folder.
+    Log.Info($"WebView2 user data folder: {userDataFolder}");
+    var env = await CoreWebView2Environment.CreateWithOptionsAsync(
+        null, userDataFolder, new CoreWebView2EnvironmentOptions());
+    await WebView.EnsureCoreWebView2Async(env);
+} catch (Exception ex) {
+    Log.Error($"WebView.EnsureCoreWebView2Async failed: {ex.Message}");
+    // Implementation of fallback error UI is not provided.
+    NativeUiError = ex.ToString();
+    return;
+}
+```
 
 **Where browser data gets stored within the UDF:**
 
 After creation of the session and UDF, browser data from your WebView2 control is stored in a subfolder of `userDataFolder`.
 
-
 ---
 
-<!-- end of "custom UDF location" tab-set -->
-
 
 <!-- ====================================================================== -->
 ## Retrieving the UDF location
@@ -435,20 +348,13 @@ After creation of the session and UDF, browser data from your WebView2 control i
 To find out what the user data folder (UDF) location was set to, use the `CoreWebView2Environment.UserDataFolder` property.  This read-only property returns the UDF location for the WebView2 session.
 
 Reasons you might want to read the UDF location:
-
 * If you want to clear browsing data from the UDF folder, such as at the end of a session.
-
 * If you want to delete the UDF.
 
-
-<!-- ====================================================================== -->
-<!-- retrieving UDF location -->
-
 ##### [Win32](#tab/win32)
 
 Use the Win32 [ICoreWebView2Environment7.get_UserDataFolder property getter](/microsoft-edge/webview2/reference/win32/icorewebview2environment7#get_userdatafolder).  That API Reference page contains example code showing how to read the `UserDataFolder` property.
 
-
 **Example code:**
 
 ```cpp
@@ -460,89 +366,71 @@ environment7->get_UserDataFolder(&userDataFolder);
 
 For examples of reading the `UserDataFolder` property, see the Win32 samples in the [WebView2Samples repo](https://github.com/MicrosoftEdge/WebView2Samples).
 
-
-<!-- ====================================================================== -->
-<!-- retrieving UDF location -->
-
 ##### [.NET (WPF/WinForms)](#tab/dotnet)
 
 <!-- Use the .NET [CoreWebView2Environment.UserDataFolder Property](/dotnet/api/microsoft.web.webview2.core.corewebview2environment.userdatafolder). -->
 
 <!-- dev: add example code to https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2environment.userdatafolder showing how to read the `UserDataFolder` property, copy that from the below code block: -->
 
-
 **Example code:**
 
 <!-- ```csharp -->
-<!-- // ADO work item "[wv2] Update .NET (WPF/WinForms) sample to add code to retrieve UDF location" - then copy lines to here
+<!-- todo: when AB#38572893 ([wv2] Update .NET (WPF/WinForms) sample to add code to retrieve UDF location) is fixed, copy code to here, add "additional" below
 <!-- ``` -->
 
 For examples of reading the `UserDataFolder` property, see the .NET (WPF/WinForms) samples in the [WebView2Samples repo](https://github.com/MicrosoftEdge/WebView2Samples).
 
-
-<!-- ====================================================================== -->
-<!-- retrieving UDF location -->
-
 ##### [ClickOnce](#tab/clickonce)
 
 Use the .NET [CoreWebView2Environment.UserDataFolder Property](/dotnet/api/microsoft.web.webview2.core.corewebview2environment.userdatafolder).
 
-
 **Example code:**
 
 <!-- ```csharp -->
-<!-- // ADO work item "[wv2] Update ClickOnce sample to add code to retrieve UDF location" - then copy lines to here
+<!-- todo: when AB#38572793 ([wv2] Update ClickOnce sample to add code to retrieve UDF location) is fixed, copy code to here, add "additional" below
 <!-- ``` -->
 
 For examples of reading the `UserDataFolder` property, see [WebView2Samples repo > webview2_sample_uwp](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/webview2_sample_uwp).
 
-
-<!-- ====================================================================== -->
-<!-- retrieving UDF location -->
-
 ##### [WinUI 2 (UWP)](#tab/uwp)
 
 Use the WinRT [CoreWebView2Environment.UserDataFolder Property](/microsoft-edge/webview2/reference/winrt/microsoft_web_webview2_core/corewebview2environment#userdatafolder).
 
-
 **Example code:**
 
 ```csharp
 private void OnGetUDFClick(object sender, RoutedEventArgs e)
 {
-    // This property can be used after WebView2 creation to find the actual location of the User Data Folder
+    // This property can be used after WebView2 creation to find the actual location of the User Data Folder.
     UserDataFolder.Text = WebView2.CoreWebView2.Environment.UserDataFolder;
 }
 ```
 
 For examples of reading the `UserDataFolder` property, see the WinUI 2 (UWP) samples in the [WebView2Samples repo > webview2_sample_uwp](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/webview2_sample_uwp).
 
-
-<!-- ====================================================================== -->
-<!-- retrieving UDF location -->
-
 ##### [WinUI 3](#tab/winui3)
 
 Use the .NET [CoreWebView2Environment.UserDataFolder Property](/dotnet/api/microsoft.web.webview2.core.corewebview2environment.userdatafolder).
 
-
 **Example code:**
 
 ```csharp
 private void OnGetUDFClick(object sender, RoutedEventArgs e)
 {
-    // This property can be used after WebView2 creation to find the actual location of the User Data Folder
+    // This property can be used after WebView2 creation to find the actual location of the User Data Folder.
     UserDataFolder.Text = WebView2.CoreWebView2.Environment.UserDataFolder;
 }
 ```
 
-<!-- For example code, see the WinUI 3 `.cs` file, at [WebView2Samples repo > WebView2_WinUI3_Sample](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/WebView2_WinUI3_Sample). -->
-
+<!--
+For example code, in [WebView2Samples repo > WebView2_WinUI3_Sample](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/WebView2_WinUI3_Sample), see:
+* [App.xaml.cs](https://github.com/MicrosoftEdge/WebView2Samples/blob/main/SampleApps/WebView2_WinUI3_Sample/WebView2_WinUI3_Sample/App.xaml.cs)
+* [MainWindow.xaml.cs](https://github.com/MicrosoftEdge/WebView2Samples/blob/main/SampleApps/WebView2_WinUI3_Sample/WebView2_WinUI3_Sample/MainWindow.xaml.cs)
+todo: which?  delete or reveal this comment?
+-->
 
 ---
 
-<!-- end of "retrieving location" tab-set -->
-
 
 <!-- ====================================================================== -->
 ## Clearing space in the UDF