MicrosoftDocs · Patrick Brosset (captainbrosset) · Aug 25, 2026 · Aug 25, 2026
diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml
@@ -33,6 +33,11 @@
           # 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 153
+          href: ./web-platform/release-notes/153.md
+          displayName: Microsoft Edge 153 web platform release notes (Sep. 2026)  # page title
+
         - name: Microsoft Edge 152
           href: ./web-platform/release-notes/152.md
           displayName: Microsoft Edge 152 web platform release notes (Aug. 2026)  # page title
@@ -69,12 +74,13 @@
           href: ./web-platform/release-notes/144.md
           displayName: Microsoft Edge 144 web platform release notes (Jan. 2026)  # page title
 
-        - name: Microsoft Edge 143
-          href: ./web-platform/release-notes/143.md
-          displayName: Microsoft Edge 143 web platform release notes (Dec. 2025)  # page title
         # keep 10 items above
         - name: Archive
           items:
+            - name: Microsoft Edge 143
+              href: ./web-platform/release-notes/143.md
+              displayName: Microsoft Edge 143 web platform release notes (Dec. 2025)  # page title
+
             - name: Microsoft Edge 142
               href: ./web-platform/release-notes/142.md
               displayName: Microsoft Edge 142 web platform release notes (Oct. 2025)  # page title

diff --git a/microsoft-edge/web-platform/release-notes/151.md b/microsoft-edge/web-platform/release-notes/151.md
@@ -34,7 +34,6 @@ To stay up-to-date and get the latest web platform features, download a preview
    * [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)
 
@@ -306,20 +305,6 @@ 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`
 

diff --git a/microsoft-edge/web-platform/release-notes/152.md b/microsoft-edge/web-platform/release-notes/152.md
@@ -21,7 +21,6 @@ To stay up-to-date and get the latest web platform features, download a preview
    * [CSS `window-drag` property](#css-window-drag-property)
    * [Media element pseudo-classes](#media-element-pseudo-classes)
 * [HTML features](#html-features)
-   * [`<camera>` and `<microphone>` elements](#camera-and-microphone-elements)
    * [Reference target](#reference-target)
    * [`autocorrect` global html attribute](#autocorrect-global-html-attribute)
 * [Web APIs](#web-apis)
@@ -114,21 +113,6 @@ See also:
 The following new HTML features are included in Microsoft Edge.
 
 
-<!-- ------------------------------ -->
-#### `<camera>` and `<microphone>` elements
-
-The `<camera>` and `<microphone>` HTML elements are browser-provided buttons that, upon activation, toggle camera or microphone streams.  If required, the button prompts the user to choose whether to grant the page access to the camera and microphone.
-
-The `<camera>` and `<microphone>` elements share the same underlying mechanism as the `<usermedia>` element, with one key distinction: they are designed to request a single capability:
-* The `<camera>` element specifically requests video capture.
-* The `<microphone>` element specifically requests audio capture.
-
-Like the `<usermedia>` element, the `<camera>` and `<microphone>` elements embed a browser-controlled, strictly styled UI into the page.  This ensures that there's a strong, intentional user signal, before a permission prompt is triggered or a stream is started.
-
-See also:
-* [`<usermedia>` element](./151.md#usermedia-element) in _Microsoft Edge 151 web platform release notes (Jul. 2026)_.
-
-
 <!-- ------------------------------ -->
 #### Reference target
 

diff --git a/microsoft-edge/web-platform/release-notes/153.md b/microsoft-edge/web-platform/release-notes/153.md
diff --git a/microsoft-edge/web-platform/release-notes/index.md b/microsoft-edge/web-platform/release-notes/index.md
@@ -16,6 +16,8 @@ To stay up-to-date and get the latest web platform features, download a preview
 <!-- 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 153 web platform release notes (Sep. 2026)](./153.md)
 * [Microsoft Edge 152 web platform release notes (Aug. 2026)](./152.md)
 * [Microsoft Edge 151 web platform release notes (Jul. 2026)](./151.md)
 * [Microsoft Edge 150 web platform release notes (Jul. 2026)](./150.md)
@@ -25,7 +27,6 @@ toc.yml - add new relnotes page, move a relnotes page to archive
 * [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)
 
 For earlier release notes, see **Archive** in the table of contents.
 

diff --git a/microsoft-edge/web-platform/site-impacting-changes.md b/microsoft-edge/web-platform/site-impacting-changes.md
@@ -36,6 +36,7 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
 | --- | --- | --- |
 | Insecure downloads over HTTP | Future release (TBD) | When a user tries to download potentially dangerous content from an HTTP site, the user will receive a UI warning, such as "Insecure download blocked."  The user will still have an option to proceed and download the item.  Admins can use the `InsecureContentAllowedForUrls` policy to specify HTTP sites for which the warning will be suppressed.  Admins can use the `InsecureDownloadWarnings` feature flag to test the impact of this upcoming feature. |
 | Deprecation of XSLT | Future release (TBD) | XSLT support represents a disproportionate attack surface, and the Chromium project which Microsoft Edge is based on has announced plans to disable and ultimately remove XSLT in a future release. See [Removing XSLT for a more secure browser](https://developer.chrome.com/docs/web-platform/deprecating-xslt). As a result, you should treat reliance on client‑side XSLT as technical debt and plan migration accordingly. Microsoft Edge version 147 introduces the XSLTEnabled feature policy to support testing and transition scenarios while the Chromium project works toward deprecating and removing XSLT support. We encourage organizations to proactively test setting `XSLTEnabled = Disabled` to identify application dependencies and remediation requirements ahead of any future default changes or removal of the feature. |
+| Remove `_current` link target | v153 | The non-standard `_current` link target, which is used to specify that a link should open in the current browsing context, is removed.  See [Removed `_current` link target](./release-notes/153.md#removed-_current-link-target) in _Microsoft Edge 153 web platform release notes (Sep. 2026)_. |
 | Deprecate unload event | v152-v155 | Edge 152 will introduce the new `unload` Permission-Policy, to allow creating unload event listeners.  The default value is initially `allow`, but between Edge 152 and Edge 155, the default value will gradually be migrated to `deny`, such that unload handlers stop firing on pages, unless a page explicitly opts in to re-enable them.  To explicitly enable unload event handlers, use the `allow` value.  <br/>Edge 152: Unload handlers will stop firing by default for 60% of page loads, unless the site explicitly enables unload handlers via the `unload` Permission-Policy.  <br/>Edge 154: Increases to 80% of page loads.  <br/>Edge 155: Increases to 100% of page loads.  <br/>This change is happening in the Chromium project, on which Microsoft Edge is based.  See [Planned deprecation of the unload event](./release-notes/152.md#planned-deprecation-of-the-unload-event) in _Microsoft Edge 152 web platform release notes (Aug. 2026)_, and [Intent to Deprecate: Deprecate unload event](https://groups.google.com/a/chromium.org/g/blink-dev/c/dvusqw9-IhI/m/SBkm_u1RAQAJ). |
 | Remove inline XSLT for production of SVG | v147 | Support for using XSLT stylesheets to transform XML data into SVG files has been removed.  See [Remove inline XSLT for production of SVG](./release-notes/147.md#remove-inline-xslt-for-production-of-svg) in _Microsoft Edge 147 web platform release notes (Apr. 2026)_. |
 | JPEG or PNG embedded in BMP | v145 | Support for embedding JPEG or PNG image data in a Bitmap image format is nonstandard, and has been removed.  See [Remove support for Bitmap extension to embed JPEG or PNG](./release-notes/145.md#remove-support-for-bitmap-extension-to-embed-jpeg-or-png) in _Microsoft Edge 145 web platform release notes (Feb. 2026)_. |

diff --git a/scripts/beta-release-notes-template.njk b/scripts/beta-release-notes-template.njk
@@ -50,10 +50,6 @@ See [What's new in DevTools (Microsoft Edge {{ data.nextBetaVersion }})](../../d
 
 See [Release notes for WebView2](../../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) ({% monthYear data.nextBetaReleaseDate %}) in _Release notes for the WebView2 SDK_.
--->
-<!-- todo: revise the above per new format: -->
-<!-- todo: when exists, use instead:
 See:
 * [Runtime nnn.n.nnnn.nn (Mmm. dd, yyyy)](../../webview2/release-notes/runtime/nnn.md)
 * [Release SDK n.n.nnnn.nn, for Runtime nnn (Mmm. dd, yyyy)](../../webview2/release-notes/sdk/n-n-nnnn-nn.md)

diff --git a/scripts/web-platform-release-notes.js b/scripts/web-platform-release-notes.js
@@ -10,10 +10,10 @@ import { execSync } from 'child_process';
 // If the number of days before the next Beta is lower or equal to DAYS_NUMBER_BEFORE_RELNOTES_NOTICE
 // then we start generating the Beta release notes.
 // This gives us time to edit, review, and publish the Beta release notes before Beta comes out.
-// This number used to be 15, which was too much because features were still moving in and out of
-// the next Beta milestone on chromestatus.com.
-// The number is now set to 7 days, which should reduce the number of last-minute changes we need to do.
-const DAYS_NUMBER_BEFORE_RELNOTES_NOTICE = 7;
+// This number is currently set to 5, which doesn't give us a lot of time to review the new Beta
+// release notes, but setting it to a higher number would mean generating the release notes very
+// early within the Beta cycle.
+const DAYS_NUMBER_BEFORE_RELNOTES_NOTICE = 5;
 
 // Where to find Edge-only origin trials info.
 const EDGE_OT_ROOT = "https://developer.microsoft.com/en-us";