@@ -4,7 +4,7 @@ browser process exit. Manually waiting for the process to exit requires
44additional work on the host app, so we are proposing the ` BrowserProcessExited `
55event. The ` ProcessFailed ` already lets app developers handle unexpected browser
66process exits for a WebView, this new API lets you listen to both expected and
7- unexpected process termination from the ` ICoreWebView2Environment ` interface so
7+ unexpected process termination from the ` ICoreWebView2Environment3 ` interface so
88you can, e.g., cleanup the user data folder when it's no longer in use. In this
99document we describe the new API. We'd appreciate your feedback.
1010
@@ -75,7 +75,7 @@ void Environment_BrowserProcessExited(object sender, CoreWebView2BrowserProcessE
7575
7676
7777# Remarks
78- Note this is an event from the ` ICoreWebView2Environment ` interface, not the
78+ Note this is an event from the ` ICoreWebView2Environment3 ` interface, not the
7979` ICoreWebView2 ` . The difference between this ` BrowserProcessExited ` event and
8080the ` CoreWebView2 ` 's ` ProcessFailed ` event is that ` BrowserProcessExited ` is
8181raised for any (expected and unexpected) ** browser process** exits, while
@@ -97,7 +97,7 @@ library WebView2
9797// ...
9898
9999/// Specifies the browser process exit type used in the
100- /// ` ICoreWebView2StagingBrowserProcessExitedEventArgs ` interface.
100+ /// ` ICoreWebView2BrowserProcessExitedEventArgs ` interface.
101101typedef enum COREWEBVIEW2_BROWSER_PROCESS_EXIT_KIND {
102102 /// Indicates that the browser process ended normally.
103103 COREWEBVIEW2_BROWSER_PROCESS_EXIT_KIND_NORMAL_EXIT,
@@ -108,7 +108,7 @@ typedef enum COREWEBVIEW2_BROWSER_PROCESS_EXIT_KIND {
108108 COREWEBVIEW2_BROWSER_PROCESS_EXIT_KIND_FAILED_EXIT
109109} COREWEBVIEW2_BROWSER_PROCESS_EXIT_KIND;
110110
111- interface ICoreWebView2Environment : IUnknown
111+ interface ICoreWebView2Environment3 : IUnknown
112112{
113113 // ...
114114
@@ -121,24 +121,24 @@ interface ICoreWebView2Environment : IUnknown
121121 /// ` remove_BrowserProcessExited ` , even if a new browser process is bound to
122122 /// this environment after earlier ` BrowserProcessExited ` events are raised.
123123 HRESULT add_BrowserProcessExited(
124- [ in] ICoreWebView2StagingBrowserProcessExitedEventHandler * eventHandler,
124+ [ in] ICoreWebView2BrowserProcessExitedEventHandler * eventHandler,
125125 [ out] EventRegistrationToken* token);
126126
127127 /// Remove an event handler previously added with ` add_BrowserProcessExited ` .
128128 HRESULT remove_BrowserProcessExited([ in] EventRegistrationToken token);
129129}
130130
131131// / Receives `BrowserProcessExited` events.
132- interface ICoreWebView2StagingBrowserProcessExitedEventHandler : IUnknown
132+ interface ICoreWebView2BrowserProcessExitedEventHandler : IUnknown
133133{
134134 /// Provides the event args for the corresponding event.
135135 HRESULT Invoke(
136136 [ in] ICoreWebView2Environment* sender,
137- [ in] ICoreWebView2StagingBrowserProcessExitedEventArgs * args);
137+ [ in] ICoreWebView2BrowserProcessExitedEventArgs * args);
138138}
139139
140140// / Event args for the `BrowserProcessExited` event.
141- interface ICoreWebView2StagingBrowserProcessExitedEventArgs : IUnknown
141+ interface ICoreWebView2BrowserProcessExitedEventArgs : IUnknown
142142{
143143 /// The kind of browser process exit that has occurred.
144144 [ propget] HRESULT BrowserProcessExitKind(
0 commit comments