I worked around the issue by using a custom capability and RPC server with fulltrust to bypass network isolation and communicate with my local server. When installed by Visual Studio, WebView1 works because it sets the flag to bypass isolation. Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT This is likely due to UWP Network isolation. Mostly connection timeouts are happening where it can't even connect on WSS. I've also noticed WebView2 has a very hard time establishing a WebSocket client connection, compared to the same script running in Chrome having no issues. _mWebView2.SetValue(WebView2.DefaultBackgroundColorProperty, ) The DependencyProperty needs to be added to the WebView2 control. Default Background Color doesn't seem to be exposed in UWP. Is it possible to set the WebView2 background transparency? If the page body is transparent you should be able to have it show through, especially for Xbox Game Bar pinned widgets which show on top of apps/games/browsers. There's a bit of fighting if you have a widget with a WebView2 on top of a Chromium browser window. I can confirm WebView2 works in Xbox Game Bar.
Is there something on the control xaml that can prevent caching? For hosted pages, the nocache headers can be used. To clear the cache I can uninstall the UWP app. WebView2 likes to cache static pages even when reloaded. LocalStorage is definitely shared across all the WebView2 controls. I could test if localSession or localStorage is shared. WebView instances share the same separate process, there is not a separate processĭo multiple WebView2 controls in the same application share memory or a context? So that you could share JS variables across controls.
Content is hosted on a separate process off the app process. Content is hosted on a background thread.
0 kommentar(er)
