Hi,

[1] Is there any way to access the EO.WebBrowser.DOM.Document object from C# code that was called from JavaScript using the eoapi.extInvoke method? We used to be able to do this in the 2017 version of EO.WebBrowser using the following code:

EO.WebBrowser.DOM.Document dom = (Document)webBrowser.WebView.GetDOMWindow().document;

However, this no longer works and returns null when using the 2022 version of EO.WebBrowser.

[2] I'm guessing the answer is probably no, but just wanted to confirm to be sure. Our code makes multiple calls back and forth between JavaScript and C# code via eoapi.extInvoke and webBrowser.WebView.EvalScript. This used to work 2017 version of EO.WebBrowser but no longer works using the 2022 version of EO.WebBrowser. It now fails with an error that looks like this:

"EvalScript failed because it is not safe to run JavaScript code at this moment. This can occur if you are inside event handlers of certain WebView events such as JSExtInvoke. In that case please consider delaying EvalScript calls until after the event handler returns."

It will take significant effort to refactor our code to avoid the multiple calls back and forth between C# and JavaScript. Is there any way to put the EO.WebBrowser into a backwards compatibility mode (e.g., an unsafe mode) to continue to do this using the 2022 version of EO.WebBrowser?

Thanks,
Gregory