Skip to content

Commit dd7b49c

Browse files
committed
promoted to stable in Release
1 parent 7ad1f86 commit dd7b49c

1 file changed

Lines changed: 31 additions & 2 deletions

File tree

  • microsoft-edge/webview2/release-notes

microsoft-edge/webview2/release-notes/index.md

Lines changed: 31 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,36 @@ For full API compatibility, this Release version of the WebView2 SDK requires We
4141
<!-- ------------------------------ -->
4242
#### Promotions
4343

44-
No additional APIs have been promoted to Stable and added in this Release SDK.
44+
The following APIs have been promoted to Stable and are now included in this Release SDK.
45+
46+
47+
<!-- ---------- -->
48+
###### Show WPF elements on top of the WebView2 layer (WebView2CompositionControl)
49+
50+
The `WebView2CompositionControl` prevents the WebView2 control from being the topmost layer in a WPF app and obscuring any WPF elements. `Microsoft.Web.WebView2.Wpf.WebView2CompositionControl` is a drop-in replacement for the standard WPF WebView2 control. Both the WebView2 control and `WebView2CompositionControl` implement the `Microsoft.Web.WebView2.Wpf.IWebView2` interface. Both of them derive from `FrameworkElement`, as follows:
51+
* `FrameworkElement` -> `HwndHost` -> `WebView2`.
52+
* `FrameworkElement` -> `Control` -> `WebView2CompositionControl`.
53+
54+
Background: If you're building a Windows Presentation Foundation (WPF) app and using the WebView2 control, you may find that your app runs into "airspace" issues, where the WebView2 control is always displayed on top, hiding any WPF elements in the same location, even if you try to specify the WPF elements to be above the WebView2 control (using visual tree order or the z-index property, for example).
55+
56+
This issue occurs because the WPF control uses the WPF `HwndHost` to host the Win32 WebView2 control, and `HwndHost` has an issue with airspace; see [Mitigating Airspace Issues In WPF Applications](https://dwayneneed.github.io/wpf/2013/02/26/mitigating-airspace-issues-in-wpf-applications.html).
57+
58+
See also:
59+
* [PR 4804: WPF Airspace - WebView2CompositionControl](https://github.com/MicrosoftEdge/WebView2Feedback/pull/4804/files?short_path=ebbc3ee#diff-ebbc3ee3560606e2823d68c134ea4aebdc1cb1252aaa9aa2b9a2815e2d8d36b2) - Spec.
60+
61+
##### [.NET/C#](#tab/dotnetcsharp)
62+
63+
* [WebView2CompositionControl Class](/dotnet/api/microsoft.web.webview2.wpf.webview2compositioncontrol?view=webview2-dotnet-1.0.3079-prerelease&preserve-view=true)
64+
65+
##### [WinRT/C#](#tab/winrtcsharp)
66+
67+
n/a
68+
69+
##### [Win32/C++](#tab/win32cpp)
70+
71+
n/a
72+
73+
---
4574

4675

4776
<!-- ------------------------------ -->
@@ -83,7 +112,7 @@ The following Experimental APIs have been added in this Prerelease SDK.
83112
###### Customize the Find behavior (Find API)
84113

85114
The Find API allows you to programmatically control **Find** operations, and enables adding the following functionality to your app:
86-
* Customize **Find** options, including **Find Term**, **Case Sensitivity**,<!-- todo: actual UI labels --> **Word Matching**, **Match Highlighting**, and **Default UI Suppression**.
115+
* Customize **Find** options, including **Find Term**, **Case Sensitivity**, **Word Matching**, **Match Highlighting**, and **Default UI Suppression**.
87116
* Find text strings and navigate among them within a WebView2 control.
88117
* Programmatically initiate **Find** operations, and navigate **Find** results.
89118
* Suppress the default **Find** UI.

0 commit comments

Comments
 (0)