You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-edge/progressive-web-apps/how-to/app-actions.md
+18-8Lines changed: 18 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
6
6
ms.topic: conceptual
7
7
ms.service: microsoft-edge
8
8
ms.subservice: pwa
9
-
ms.date: 05/19/2025
9
+
ms.date: 06/24/2025
10
10
---
11
11
# Enable App Actions on Windows for a PWA
12
12
@@ -262,9 +262,7 @@ The above code is not in [Demos/wami/manifest.json](https://github.com/Microsoft
262
262
263
263
At the current stage, your PWA needs to be packaged as a Microsoft Store PWA, to be called by the Windows App Actions framework. You must use Microsoft Edge 137 or greater.
264
264
265
-
The Stable release of Edge 137 will be available on May 29, 2025. If you'd like to try it out before May 29, 2025, you can package your PWA in Edge Canary; see [Package a store PWA in Edge Canary](#package-a-store-pwa-in-edge-canary), below.
266
-
267
-
1. Upgrade to Edge Stable 137 version. (Edge 137 stable will be available after May 29, 2025.)
265
+
1. Upgrade to Edge Stable 137 version.
268
266
269
267
1. Package your PWA for [PWABuilder.com](https://www.pwabuilder.com); see [Package your PWA for the Store](./microsoft-store.md#package-your-pwa-for-the-store) in _Publish a PWA to the Microsoft Store_.
270
268
@@ -276,19 +274,31 @@ The Stable release of Edge 137 will be available on May 29, 2025. If you'd like
276
274
277
275
1. Click the **Download** button.
278
276
279
-
1. Unzip your download archive. Then you can [publish your PWA to the Microsoft Store](./microsoft-store.md) and install the app from the Store, or install it directly by running `install.ps1`.
277
+
1. Unzip your download archive. Install it by running `install.ps1`.
280
278
281
279
1. Launch your PWA by clicking the PWA icon.
282
280
281
+
1. Test your PWA actions locally by following [Test App Actions for a PWA](#test-app-actions-for-a-pwa), below, to validate the functionality.
282
+
283
+
1. Open the action definition manifest file (such as `ActionsManifest.json`) that you used when packaging in PWAbuilder.com.
284
+
285
+
1. Set the initial availability of each of the app actions to `false`, as described in [Set initial availability](/windows/ai/app-actions/actions-availability#set-initial-availability) in _Toggle availability of an App Action for Windows_.
286
+
287
+
Before publishing your package, we recommend the above step. If you don't set the initial availability of the app action to `false`, your action will only work if the user manually goes to `edge://flags` in Microsoft Edge and then enables the feature flag `#edge-app-actions-on-windows-for-web-apps`.
288
+
289
+
Setting the initial availability to `false` is needed because Microsoft Edge's support of App Actions on Windows in PWAs is controlled by the feature flag `#edge-app-actions-on-windows-for-web-apps`, and is disabled by default, because this is a new feature in the Edge browser and is currently in Developer Trial<!-- not Origin Trial--> stage, as of June 26, 2025.
290
+
291
+
When the feature flag `#edge-app-actions-on-windows-for-web-apps` is officially rolled out (later in 2025),<!-- todo: update after rolled out --> Microsoft Edge will automatically switch the actions that you defined in the action definition manifest file from `Disabled` to `Enabled`, allowing end users to utilize your app's actions without requiring any further changes on your part.
292
+
293
+
1. Publish your PWA, as described in [Publish a PWA to the Microsoft Store](/microsoft-edge/progressive-web-apps-chromium/how-to/microsoft-store).
The Stable release of Edge 137 will be available on May 29, 2025; see [Package a store PWA in Edge Stable](#package-a-store-pwa-in-edge-stable), above.
288
-
289
299
Edge Canary gives a preview of the functionalities that's not available in stable yet.
290
300
291
-
If you want to try out App Actions for PWAs before May 29, 2025, you can package your PWA in Edge Canary, as follows:
301
+
If you want to try out the latest capabilities of App Actions in Edge Canary, you can package your PWA in Edge Canary, as follows:
292
302
293
303
1. Install [Edge Canary](https://www.microsoft.com/edge/download/insider) and upgrade to the latest version.
Copy file name to clipboardExpand all lines: microsoft-edge/webview2/concepts/versioning.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,17 +30,15 @@ New APIs are introduced in phases as follows:
30
30
31
31
| API status | Description |
32
32
|---|---|
33
-
|_Experimental_| 1. First an API is Experimental in a Prerelease SDK. You can test these APIs and provide feedback. The API isn't in a Release SDK yet. |
33
+
|_Experimental in a Prerelease SDK_| 1. First an API is Experimental in a Prerelease SDK. You can test these APIs and provide feedback. The API isn't in a Release SDK yet. |
34
34
|_Stable in a Prerelease SDK_| 2. Then the API is promoted to Stable in the Prerelease SDK. The API isn't in a Release SDK yet. |
35
35
|_Stable in a Release SDK_| 3. Then the Stable API is promoted to be included in the Release SDK. This typically happens 1 month after the API is promoted to Stable in a Prerelease SDK. The API also remains in the Prerelease SDK. |
36
36
37
37

38
38
<!-- .png is used by webview2/release-notes/about.md and webview2/concepts/versioning.md -->
39
39
40
-
<!-- terminology:
41
-
APIs are Experimental or Stable
42
-
SDKs/packages are Prerelease or Release
43
-
-->
40
+
See also:
41
+
*[Phases of adding APIs](../release-notes/about.md#phases-of-adding-apis) in _About Release Notes for the WebView2 SDK_.
1. APIs are initially introduced as Experimental APIs in a Prerelease SDK package.
30
-
1. Then they become Stable APIs in a Prerelease SDK package.
31
-
1. Soon after, they become Stable APIs in a Release SDK package. Sometimes, APIs are simultaneously promoted to Stable in a Prerelease SDK and Stable in a Release SDK.
28
+
New APIs are added in three phases, as follows:
29
+
30
+
1. APIs are initially introduced as Experimental APIs in a Prerelease SDK package. In Win32, the type name includes the word "Experimental".
31
+
32
+
1. Then the APIs become Stable APIs in a Prerelease SDK package. In Win32, the type name omits the word "Experimental".
33
+
34
+
1. Soon after, the APIs become Stable APIs in a Release SDK package. Sometimes, APIs are simultaneously promoted to Stable in a Prerelease SDK and Stable in a Release SDK.
32
35
33
36

34
37
<!-- .png is used by webview2/release-notes/about.md and webview2/concepts/versioning.md -->
35
38
39
+
Shorthand names of the phases:
40
+
41
+
1. Experimental in Prerelease
42
+
1. Stable in Prerelease
43
+
1. Stable in Release
44
+
45
+
Release Notes sections use this wording for the phases:
46
+
47
+
* The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.
48
+
49
+
* The following APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, and are included in this Prerelease SDK.
50
+
51
+
* The following APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, and are now included in this Release SDK.
52
+
36
53
See also:
37
54
*[Phases of introducing APIs](../concepts/versioning.md#phases-of-introducing-apis) in _Prerelease and Release SDKs for WebView2_.
Copy file name to clipboardExpand all lines: microsoft-edge/webview2/release-notes/archive.md
+95-5Lines changed: 95 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,100 @@ ms.author: msedgedevrel
6
6
ms.topic: conceptual
7
7
ms.service: microsoft-edge
8
8
ms.subservice: devtools
9
-
ms.date: 06/03/2025
9
+
ms.date: 06/30/2025
10
10
---
11
11
# Archived Release Notes for the WebView2 SDK
12
12
13
13
These Release Notes provide information about added features and bug fixes that are included in the WebView2 Release SDK and the WebView2 Prerelease SDK, for older releases.
[NuGet package for WebView2 SDK 1.0.3116-prerelease](https://www.nuget.org/packages/Microsoft.Web.WebView2/1.0.3116-prerelease)
53
+
54
+
For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 134.0.3116.0 or higher.
55
+
56
+
57
+
<!-- ------------------------------ -->
58
+
#### Experimental APIs
59
+
60
+
No Experimental APIs have been added in this Prerelease SDK.
61
+
62
+
63
+
<!-- ------------------------------ -->
64
+
#### Promotions
65
+
66
+
No APIs have been promoted from Experimental to Stable in this Prerelease SDK.
67
+
68
+
69
+
70
+
<!-- ------------------------------ -->
71
+
#### Bug fixes
72
+
73
+
74
+
<!-- ---------- -->
75
+
###### Runtime-only
76
+
77
+
* Added the missing **Close** button in the **Download** flyout.
78
+
* Fixed a race condition that occurred when the Web Request Response event never occurs.
79
+
80
+
81
+
<!-- ---------- -->
82
+
###### SDK-only
83
+
84
+
* Fixed .NET and Win32 documentation of the `CoreWebView2Find.FindNext` method that incorrectly mentioned `FindPrevious`. The method summary now mentions `FindNext` instead. ([Issue #5059](https://github.com/MicrosoftEdge/WebView2Feedback/issues/5059))
[NuGet package for WebView2 SDK 1.0.####-prerelease](https://www.nuget.org/packages/Microsoft.Web.WebView2/1.0.####-prerelease)
64
+
65
+
For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version ###.0.####.0 or higher.
66
+
67
+
68
+
<!-- ------------------------------ -->
69
+
#### Experimental APIs
70
+
71
+
No Experimental APIs have been added in this Prerelease SDK.
72
+
The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.
73
+
74
+
75
+
<!-- ---------- -->
76
+
###### heading
77
+
78
+
description
79
+
80
+
##### [.NET/C#](#tab/dotnetcsharp)
81
+
82
+
##### [WinRT/C#](#tab/winrtcsharp)
83
+
84
+
##### [Win32/C++](#tab/win32cpp)
85
+
86
+
---
87
+
88
+
89
+
<!-- ------------------------------ -->
90
+
#### Promotions
91
+
92
+
No APIs have been promoted from Experimental to Stable in this Prerelease SDK.
93
+
The following APIs have been promoted from Phase 1: Experimental in Prerelease, to Phase 2: Stable in Prerelease, and are included in this Prerelease SDK.
0 commit comments