Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 17 additions & 9 deletions microsoft-edge/toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -1511,7 +1511,10 @@
- name: Release notes for the WebView2 Runtime
href: ./webview2/release-notes/runtime/index.md

- name: Preview Runtime 153.0.4234.6 (Aug. 28, 2026)
- name: Preview Runtime 154.0.4258.9 (Sep. 10, 2026)
href: ./webview2/release-notes/runtime/154.md

- name: Runtime 153.0.4234.32 (Sep. 11, 2026)
href: ./webview2/release-notes/runtime/153.md

- name: Runtime 152.0.4191.53 (Aug. 28, 2026)
Expand Down Expand Up @@ -1753,6 +1756,9 @@
- name: Release notes for WebView2 SDKs
href: ./webview2/release-notes/sdk/index.md

- name: SDK 1.0.4255-prerelease, for Runtime 154 (Sep. 11, 2026)
href: ./webview2/release-notes/sdk/1-0-4255-prerelease.md

- name: SDK 1.0.4191.47, for Runtime 152 (Aug. 28, 2026)
href: ./webview2/release-notes/sdk/1-0-4191-47.md

Expand Down Expand Up @@ -2378,9 +2384,6 @@
# -----------------------------------------------------------------------------
- name: Test and automation for WebView2 apps
items:
- name: Test upcoming APIs and features
href: ./webview2/how-to/set-preview-channel.md

- name: Use the Chrome DevTools Protocol (CDP) in WebView2 apps
href: ./webview2/how-to/chromium-devtools-protocol.md
displayName: chrome developer protocol # catch mis-expansion
Expand All @@ -2391,12 +2394,17 @@
- name: Automate and test WebView2 apps with Microsoft Edge WebDriver
href: ./webview2/how-to/webdriver.md

- name: Prerelease testing using preview channels
href: ./webview2/how-to/prerelease-testing.md
- name: Prerelease testing using preview channels of Microsoft Edge
items:
- name: Prerelease testing using preview channels of Microsoft Edge
href: ./webview2/how-to/prerelease-testing.md

- name: Switch to a preview channel to test upcoming APIs and features
href: ./webview2/how-to/set-preview-channel.md

- name: Self-host by deploying preview channels
href: ./webview2/how-to/self-hosting.md
displayName: self-hosting
- name: Self-host by deploying preview channels
href: ./webview2/how-to/self-hosting.md
displayName: self-hosting
# -----------------------------------------------------------------------------
- name: Debug WebView2 apps
items:
Expand Down
7 changes: 2 additions & 5 deletions microsoft-edge/web-platform/release-notes/153.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,12 +45,9 @@ See [What's new in DevTools (Microsoft Edge 153)](../../devtools/whats-new/153.m
<!-- ====================================================================== -->
## WebView2

See [Release notes for WebView2](../../webview2/release-notes/index.md).
<!-- todo: when exists for 153, use instead:
See:
* [Runtime 153.n.nnnn.nn (Mmm. dd, yyyy)](../../webview2/release-notes/runtime/nnn.md)
* [Release SDK n.n.nnnn.nn, for Runtime 153 (Mmm. dd, yyyy)](../../webview2/release-notes/sdk/n-n-nnnn-nn.md)
-->
* [Runtime 153.0.4234.32 (Sep. 11, 2026)](../../webview2/release-notes/runtime/153.md)
<!-- * [Release SDK n.n.nnnn.nn, for Runtime 153 (Mmm. dd, yyyy)](../../webview2/release-notes/sdk/n-n-nnnn-nn.md) -->


<!-- ====================================================================== -->
Expand Down
14 changes: 5 additions & 9 deletions microsoft-edge/web-platform/release-notes/154.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,12 +48,8 @@ See [What's new in DevTools (Microsoft Edge 154)](../../devtools/whats-new/154.m
<!-- ====================================================================== -->
## WebView2

See [Release notes for WebView2](../../webview2/release-notes/index.md).
<!-- 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)
-->
* [Preview Runtime 154.0.4258.9 (Sep. 10, 2026)](../../webview2/release-notes/runtime/154.md)


<!-- ====================================================================== -->
Expand Down Expand Up @@ -316,21 +312,21 @@ For the full list of available origin trials, see [Microsoft Edge Origin Trials]
| Declarative CSS Module Scripts | Shares declarative stylesheets with shadow roots, including declarative shadow roots, by using inline style modules. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/966b04dd-3da4-43f4-a6a0-66a785f129f4) |
| 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) |
| Control viewport heuristics in Speculation Rules API<!-- new --> | Lets you control the viewport heuristics that are used by speculation rules, to determine if different heuristics parameters give you better results than the default ones. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/d5e83bc7-0388-4994-bbb4-9b89cdd19e56) |
| Control viewport heuristics in Speculation Rules API | Lets you control the viewport heuristics that are used by speculation rules, to determine if different heuristics parameters give you better results than the default ones. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/d5e83bc7-0388-4994-bbb4-9b89cdd19e56) |
| 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) |
| `PrefetchAndPrerenderActivationBeacon`<!-- new --> | Allows Edge to reliably report an activation beacon when a prefetch or prerendered page is activated. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/c464cbce-0067-459e-a232-417ecc558191) |
| `PrefetchAndPrerenderActivationBeacon` | Allows Edge to reliably report an activation beacon when a prefetch or prerendered page is activated. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/c464cbce-0067-459e-a232-417ecc558191) |
| HTML in canvas | Enables rendering HTML in a canvas by using new drawing methods and the `paint` event. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/a297467e-0030-4c4c-8739-48e130026c03) |
| 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 that's 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) |
| 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) |
| WebRTC Data Channel: SCTP Negotiation Acceleration Protocol (SNAP) | SNAP reduces WebRTC data channel startup latency by embedding SCTP connection setup parameters in the SDP offer/answer exchange. Because WebRTC already uses DTLS to establish a secure channel, the separate SCTP handshake can be avoided, saving up to two network round trips and enabling faster data channel establishment. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/fd803c89-97ff-4d0d-bc23-641b6041cb12) |
| WebRTC Diagnostic Logging API<!-- new --> | Collects internal diagnostic logs for WebRTC-related operations. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/87bfe66a-bead-4260-bb55-b2f6be05bd93) |
| WebRTC Diagnostic Logging API | Collects internal diagnostic logs for WebRTC-related operations. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/87bfe66a-bead-4260-bb55-b2f6be05bd93) |
| Gamepad raw input event | Instead of relying on frequent polling via `navigator.getGamepads()`, webpages 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) |
| 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) |
| 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) |
| JS Self-Profiling Markers | Extends the JS Self-Profiling API with sample markers such as `script`, `gc`, `style`, `layout`, and `paint`. These markers identify the activity that the browser was doing at capture time. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/ad17726e-aab6-42a0-8d63-0888419e5ad3) |
| Declarative Performance Observer API<!-- new --> | The Declarative Performance Observer API uses HTTP response headers to prove a reliable browser-managed telemetry system that reports performance metrics for the site, from navigation initiation to page termination. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/26ae2f49-86eb-4aa6-a113-a875e32502c8) |
| Declarative Performance Observer API | Uses HTTP response headers to prove a reliable browser-managed telemetry system that reports performance metrics for the site, from navigation initiation to page termination. | [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/26ae2f49-86eb-4aa6-a113-a875e32502c8) |


<!-- ====================================================================== -->
Expand Down
4 changes: 2 additions & 2 deletions microsoft-edge/webview2/concepts/developer-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ When using the Evergreen WebView2 Runtime, run forward-compatibility tests by us

Because the Evergreen Runtime updates automatically, you should regularly run compatibility tests to ensure that your WebView2 app will continue to work as expected on the new Runtime version. This can be done by testing your web content in the WebView2 control against the Microsoft Edge preview channels.

Follow the guidance in [Prerelease testing using preview channels](../how-to/prerelease-testing.md) and [Self-host by deploying preview channels](../how-to/self-hosting.md).
Follow the guidance in [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md) and [Self-host by deploying preview channels](../how-to/self-hosting.md).


<!-- ------------------------------ -->
Expand Down Expand Up @@ -146,7 +146,7 @@ Follow the guidance in [Develop secure WebView2 apps](./security.md).
* [The Fixed Version runtime distribution mode](./distribution.md#the-fixed-version-runtime-distribution-mode) in _Distribute your app and the WebView2 Runtime_.
* [Handle Evergreen WebView2 Runtime updates](./distribution.md#handle-evergreen-webview2-runtime-updates) in _Distribute your app and the WebView2 Runtime_.
* [Develop secure WebView2 apps](./security.md)<!-- bucket 7 -->
* [Prerelease testing using preview channels](../how-to/prerelease-testing.md)<!-- bucket 8 bottom -->
* [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md)<!-- bucket 8 bottom -->
* [Self-host by deploying preview channels](../how-to/self-hosting.md)<!-- bucket 8 very bottom -->
* [Manage user data folders](./user-data-folder.md)<!-- bucket 11 -->

Expand Down
8 changes: 4 additions & 4 deletions microsoft-edge/webview2/concepts/distribution.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ During development and testing, a WebView2 app can use either option as the back

* The WebView2 Runtime. The Runtime generally provides the same web platform capabilities and update release cadence as the Stable channel of the Microsoft Edge browser; see [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule). Use the WebView2 Runtime in a production environment or to develop and test against the web platform that your users have today.

* A preview (Insider) Microsoft Edge browser channel. These Microsoft Edge preview channels are Beta, Dev, and Canary. Use this approach to test your app for forward-compatibility, so that you know if a breaking change is coming that will require updating your app. See [Test upcoming APIs and features](../how-to/set-preview-channel.md).
* A preview (Insider) Microsoft Edge browser channel. These Microsoft Edge preview channels are Beta, Dev, and Canary. Use this approach to test your app for forward-compatibility, so that you know if a breaking change is coming that will require updating your app. See [Switch to a preview channel to test upcoming APIs and features](../how-to/set-preview-channel.md).

A production release of a WebView2 app can only use the WebView2 Runtime as the backing web platform, not Microsoft Edge.

Expand Down Expand Up @@ -224,7 +224,7 @@ To use the new version of the WebView2 Runtime, you need to either release all r

In the Evergreen distribution mode, the WebView2 Runtime is automatically kept up to date on the client to provide the latest features and security fixes. If you use Evergreen distribution, to ensure that your WebView2 app stays compatible with the web, you should set up testing infrastructure.

For best practices about how to test your app for forward-compatibility, see [Prerelease testing using preview channels](../how-to/prerelease-testing.md) and [Self-host by deploying preview channels](../how-to/self-hosting.md).
For best practices about how to test your app for forward-compatibility, see [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md) and [Self-host by deploying preview channels](../how-to/self-hosting.md).


<!-- ------------------------------ -->
Expand Down Expand Up @@ -360,8 +360,8 @@ Example managed app folder structure:
* [Feature-detecting to test whether the installed Runtime supports recently added APIs](./versioning.md#feature-detecting-to-test-whether-the-installed-runtime-supports-recently-added-apis) in _Prerelease and Release SDKs for WebView2_.
* [Evergreen vs. fixed version of the WebView2 Runtime](./evergreen-vs-fixed-version.md)<!-- toc bucket 6 leaf 3 -->
* [Windows Server Update Services (WSUS)](./enterprise.md#windows-server-update-services-wsus) in _Enterprise management of WebView2_.<!-- toc bucket 6 leaf 4 -->
* [Test upcoming APIs and features](../how-to/set-preview-channel.md)<!-- toc bucket 8 top -->
* [Prerelease testing using preview channels](../how-to/prerelease-testing.md)<!-- toc bucket 8 bottom -->
* [Switch to a preview channel to test upcoming APIs and features](../how-to/set-preview-channel.md)<!-- toc bucket 8 top -->
* [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md)<!-- toc bucket 8 bottom -->
* [Self-host by deploying preview channels](../how-to/self-hosting.md)<!-- toc bucket 8 very bottom -->
* [Distribute a WebView2 app as a single executable file](../how-to/static.md) - statically linking the WebView2 loader library.

Expand Down
4 changes: 2 additions & 2 deletions microsoft-edge/webview2/concepts/overview-features-apis.md
Original file line number Diff line number Diff line change
Expand Up @@ -3681,8 +3681,8 @@ Runtime selection supports prerelease testing and self-hosting. When creating a
* To specify which browser preview channels are searched for, use the `CoreWebView2EnvironmentOptions.ReleaseChannels` property.

See also:
* [Test upcoming APIs and features](../how-to/set-preview-channel.md)
* [Prerelease testing using preview channels](../how-to/prerelease-testing.md)
* [Switch to a preview channel to test upcoming APIs and features](../how-to/set-preview-channel.md)
* [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md)
* [Self-host by deploying preview channels](../how-to/self-hosting.md)

##### [.NET/C#](#tab/dotnetcsharp)
Expand Down
Loading
Loading