David Risney
David Risney
Thanks! Looks like a regression we'll need to fix. I've marked it tracked to get it in our bug database.
Thanks for your detailed issue. Unfortunately, at the moment its a known limitation that printing in a UWP app is not supported. This is described a bit more in the...
Thanks for the feedback! To run script we must go cross process to the renderer process and run the script and so ExecuteScript really is asynchronous. A synchronous version of...
Yes the issue is there's no good solution that will work for everyone. 1. If you run WebView2 on the same UI thread as the rest of your app code...
In the above you have `anotherBox.value = chrome.webview.hostObjects.abcObj.GetBoxText();` but that seems to be mixing async proxy and sync proxy semantics. Do you actually mean one of the following: a. `anotherBox.value...
In my (2) above about calling from a different thread I meant you could have the calling thread communicate to the WebView2 UI thread to call ExecuteScript and then wait...
I've tried the following in our WebView2 API Sample app and it seems to be working OK. This would be an example of (1) above. But again CoWait could be...
Reassigning to @champnic in case he or @bradp0721 would have questions or comments regarding this. Thanks.
I don't believe this is intended to be supported previously. @champnic or @bradp0721 should know better.
Apologies, how do you make the error occur? Can you show the code that is running when the exception occurs?