Skip to content

Commit f241806

Browse files
mikehoffmssivMSFT
andauthored
WebView2 Release Notes for May 2025 Release SDK (#3427)
* templates * link to Edge schedule * Draft v1 May relnotes * writer pass * openajax --------- Co-authored-by: sivMSFT <v-bacprasad@microsoft.com>
1 parent b62e5fa commit f241806

File tree

15 files changed

+295
-172
lines changed

15 files changed

+295
-172
lines changed

microsoft-edge/accessibility/build/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ JavaScript library to help modern web applications with accessibility concerns b
171171
<!-- ------------------------------ -->
172172
#### OpenAjax examples
173173

174-
The [OpenAjax Alliance website](http://oaa-accessibility.org) is an excellent resource for verifying the rules for WAI-ARIA and provides a number of examples of WAI-ARIA implementations.
174+
[OpenAjax Alliance](http://www.openajax.org) is an excellent resource for verifying the rules for WAI-ARIA and provides a number of examples of WAI-ARIA implementations.
175175

176176

177177
<!-- ------------------------------ -->

microsoft-edge/webview2/concepts/deployment-distribution.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,3 +17,10 @@ Articles in this section:
1717
* [Enterprise management of WebView2 Runtimes](enterprise.md).
1818
* [Distribute an app as a single executable file](../how-to/static.md) - How to statically link the WebView2 loader library, to create a single-file app.
1919
* [Publish a UWP WebView2 app to the Microsoft Store](../how-to/publish-uwp-app-store.md)
20+
21+
22+
<!-- ====================================================================== -->
23+
## See also
24+
25+
<!-- External: -->
26+
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)

microsoft-edge/webview2/concepts/developer-guide.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,3 +111,11 @@ WebView2 enables you to host web content in your native applications, providing
111111
However, hosting web content can also introduce vulnerabilities. To avoid vulnerabilities that can arise from hosting web content within a native application, make sure to design your WebView2 application to closely monitor interactions between the web content and the host application.
112112

113113
Follow the guidance in [Develop secure WebView2 apps](../concepts/security.md).
114+
115+
116+
<!-- ====================================================================== -->
117+
## See also
118+
<!-- todo: all links in article body -->
119+
120+
<!-- External: -->
121+
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)

microsoft-edge/webview2/concepts/distribution.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -418,3 +418,10 @@ Example managed app folder structure:
418418
\win-x64\native\WebView2Loader.dll (x64)
419419
\win-x86\native\WebView2Loader.dll (x86)
420420
```
421+
422+
423+
<!-- ====================================================================== -->
424+
## See also
425+
426+
<!-- External: -->
427+
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)

microsoft-edge/webview2/concepts/end-user-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ There are normally a few processes:
3939
* Utility processes, such as network or audio, depending on the content.
4040
* Renderer processes.
4141

42-
Your machine will have one set of processes for each app that uses WebView2, and typically one renderer process for each WebView2 control that's in the app, similar to how you have one renderer process per tab in a browser. For details, see [Process model for WebView2 apps](/microsoft-edge/webview2/concepts/process-model).
42+
Your machine will have one set of processes for each app that uses WebView2, and typically one renderer process for each WebView2 control that's in the app, similar to how you have one renderer process per tab in a browser. For details, see [Process model for WebView2 apps](./process-model.md).
4343

4444

4545
<!-- ====================================================================== -->

microsoft-edge/webview2/concepts/enterprise.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,4 +63,7 @@ WebView2 options in Configuration Manager exist under the Microsoft Edge Managem
6363
<!-- ====================================================================== -->
6464
## See also
6565

66-
* [Distribute your app and the WebView2 Runtime](distribution.md) - About the Evergreen, self-updating WebView2 Runtime.
66+
* [Distribute your app and the WebView2 Runtime](./distribution.md) - About the Evergreen, self-updating WebView2 Runtime.
67+
68+
<!-- External: -->
69+
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)

microsoft-edge/webview2/concepts/versioning.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -185,3 +185,10 @@ When you develop a WebView2 app using a recent version of the WebView2 SDK, if y
185185
* **.NET and WinUI**. Use `try/catch` and check for a `No such interface supported` exception when using methods, properties, and events that were added to more recent versions of the WebView2 SDK. This exception likely indicates that the client's WebView2 Runtime is an older version that doesn't support that API.
186186

187187
If your code determines that an API is unavailable in the client's installed WebView2 Runtime, you should provide graceful fallback for the associated feature, or inform the user that they must update the WebView2 Runtime to use the feature.
188+
189+
190+
<!-- ====================================================================== -->
191+
## See also
192+
193+
<!-- External: -->
194+
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)

microsoft-edge/webview2/how-to/prerelease-testing.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,9 @@ Upon finding issues, you can report them via the [Microsoft Edge / WebView2Feedb
6161

6262
* [Self-host by deploying preview channels](./self-hosting.md)
6363
* [Test upcoming APIs and features](./set-preview-channel.md)
64-
* [Automate and test WebView2 apps with Microsoft Edge WebDriver](/microsoft-edge/webdriver)
64+
* [Automate and test WebView2 apps with Microsoft Edge WebDriver](./webdriver.md)
65+
* [Site compatibility-impacting changes coming to Microsoft Edge](../../web-platform/site-impacting-changes.md)
6566
* [WebView2 feedback repo](https://github.com/MicrosoftEdge/WebView2Feedback)
66-
* [Site compatibility-impacting changes coming to Microsoft Edge](/microsoft-edge/web-platform/site-impacting-changes)
67+
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)
6768
* [Overview of the Microsoft Edge channels](/deployedge/microsoft-edge-channels)
6869
* [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider) - download a preview channel of Microsoft Edge (Beta, Dev, or Canary).

microsoft-edge/webview2/how-to/self-hosting.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,9 @@ If you are using the API, then we recommend building UI in your app that allows
8585

8686
* [Test upcoming APIs and features](./set-preview-channel.md)
8787
* [Prerelease testing using preview channels](./prerelease-testing.md)
88-
* [WebView2 feedback repo](https://github.com/MicrosoftEdge/WebView2Feedback)
8988
* [Site compatibility-impacting changes coming to Microsoft Edge](../../web-platform/site-impacting-changes.md)
89+
90+
External:
91+
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)
92+
* [WebView2 feedback repo](https://github.com/MicrosoftEdge/WebView2Feedback)
9093
* [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider) - download the Canary, Dev, or Beta channel of Microsoft Edge.

microsoft-edge/webview2/how-to/set-preview-channel.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -426,5 +426,22 @@ In your app's code, write your own custom logic to deploy the latest version of
426426

427427
<!-- ====================================================================== -->
428428
## See also
429+
<!-- all links in article body -->
429430

431+
* [Prerelease testing using preview channels](./prerelease-testing.md)
432+
* [Self-host by deploying preview channels](./self-hosting.md)
430433
* [Phases of introducing APIs](../concepts/versioning.md#phases-of-introducing-apis) in _Prerelease and Release SDKs for WebView2_.
434+
* [Distribute your app and the WebView2 Runtime](../concepts/distribution.md)
435+
* [Prerelease and Release SDKs for WebView2](../concepts/versioning.md)
436+
437+
Enterprise docs:
438+
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)
439+
* [Configure Microsoft Edge policy settings on Windows devices](/deployedge/configure-microsoft-edge)
440+
441+
Microsoft Intune:
442+
* [Configure Microsoft Edge policy settings in Microsoft Intune](/mem/intune/configuration/administrative-templates-configure-edge)
443+
* [Configure Microsoft Edge policy settings with Microsoft Intune](/deployedge/configure-edge-with-intune)
444+
445+
Versions and preview channels of Microsoft Edge:
446+
* [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider)
447+
* [Download and configure Microsoft Edge for Business](https://www.microsoft.com/edge/business/download)

0 commit comments

Comments
 (0)