http://bugs.winehq.org/show_bug.cgi?id=58921 --- Comment #11 from brandow <brandowlucas@gmail.com> --- In my case, using the staging dcomp-DCompositionCreateDevice2 patchset + msedgewebview2.exe set to win10 still makes NinjaTrader's embedded "Chat" WebView2 render completely black. WebView2 itself is running since the right click context menu and the separate DevTools window render correctly. Only the embedded Chat content page stays black. Just using the staging patchset will also loop and memory hog while logging those errors: 05b0:fixme:dcomp:DCompositionCreateDevice3 0000000000E59230, {5f4633fe-1e08-4cb8-8c75-ce24333f5602}, 000000000091E418. 05b0:fixme:dcomp:device_QueryInterface {4ca97a18-cbfd-4b0d-89e1-f7fa86d8d63e} not implemented, returning E_NOINTERFACE I'm not sure if those errors are directly causing the loop/memory hog though. Nevertheless, I used the github.com/giang17/wine DirectComposition fork with a local change hack I did (https://github.com/BrandowLucas/wine-dcomp/commit/159ce338f82aa820cd7bc65fe2...), and it now renders NinjaTrader's embedded Chat WebView2 successfully with win10/DComp. With WebView2 109.0.1518.140, the Win7 workaround also wouldn't do it in my case. The embedded window only worked when using win10 and the DComp implementation from the custom fork. I didn't bother checking whether it is possible to fix WebView2's legacy Windows 7 rendering path without DComp. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.