2 way javascript interop is possible right now?

[danilobreda]

Javascript call C# and C# call Javascript ?

[nmoschkin]

#2

please refer to my answer, here.

[nmoschkin]

Okay. I have created the code for this. You may test it.

[nmoschkin]

Note: Both Windows support and EvaluateJavaScriptAsync support are in the windows-maui-support branch and will be merged, soon.

[nmoschkin]

@danilobreda have you had a chance to test it yet?

[danilobreda]

@nmoschkin not yet, i will test it soon, thanks for the work :)

[ibc-shane-kelly]

@nmoschkin, thanks for this code we are getting further with it than other options out there. I have tested the windows implementation and it is all working well. I am running on iOS now and JavaScript to C# is working but not C# to JavaScript. I will test android tomorrow. I'll let you know what I find.

Quick edit I got the iOS version to work by updating the VirtualView_RequestEvaluateJavaScript function in the iOS HybridWebViewHandler to be

private void VirtualView_RequestEvaluateJavaScript(object sender, EvaluateJavaScriptAsyncRequest e)
{
sync.Post((o) =>
{
PlatformView.EvaluateJavaScript(e);
}, null);
}

Happy to be corrected if there is a better way to do it.

[ibc-shane-kelly]

Now tested in Android as well and working well.

Thanks again!!

[nmoschkin]

@nmoschkin, thanks for this code we are getting further with it than other options out there. I have tested the windows implementation and it is all working well. I am running on iOS now and JavaScript to C# is working but not C# to JavaScript. I will test android tomorrow. I'll let you know what I find.

Quick edit I got the iOS version to work by updating the VirtualView_RequestEvaluateJavaScript function in the iOS HybridWebViewHandler to be

private void VirtualView_RequestEvaluateJavaScript(object sender, EvaluateJavaScriptAsyncRequest e) { sync.Post((o) => { PlatformView.EvaluateJavaScript(e); }, null); }

Happy to be corrected if there is a better way to do it.

yes. If something fails on iOS, call it from the main thread to see if that fixes it before doing anything else. iOS is very temperamental when it comes to demanding that certain things are always invoked on the main thread. I did not see this particular issue because at the time, I didn't have a working iOS test platform (this was during that most recent bug that came from upgrading to XCode 14)