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: specs/LaunchingRegisteredProtocols.md
+15-30Lines changed: 15 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,13 @@
1
1
# Background
2
2
3
-
We are exposing an event that will be raised when an attempt to launch an external protocol is made. The host will be given the option to cancel the launch as well as hide the default dialog and display a custom dialog.
3
+
We are exposing an event that will be raised when an attempt to launch an external protocol is made. The host will be given the option to cancel the launch. Cancelling the launch gives the host the opportunity to hide the default dialog, display a custom dialog, and then launch the external protocol themselves.
4
4
5
5
# Description
6
6
7
7
This event will be raised before the external protocol launch occurs. When an attempt to launch an external protocol is made, the default dialog is displayed in which the user can select `Open` or `Cancel`. The `NavigationStarting`, `NavigationCompleted`, `SourceChanged`, `ContentLoading`, and `HistoryChanged` events will not be raised when a request is made to launch an external protocol.
8
8
9
9
The `LaunchingExternalProtocol` event will be raised on the `CoreWebView2` interface.
10
10
11
-
The host may set the `Cancel` or `Handled` event args which would result in the following behavior:
12
-
13
-
| Cancel | Handled | Outcome |
14
-
|-|-|-|
15
-
| False | False | Default dialog shown, URI optionally launched based on end user input |
16
-
| False | True | No dialog, URI is launched |
17
-
| True | * | No dialog shown, URI is not launched |
0 commit comments