WebView compatibility between RH7 and RH8 with `Eto.Forms`

[Will_Wang]

Picking up on a loose thread:

Eto.Forms Styling

@David_Moreau Do you have an example that shows what you’re trying to do? Do note that you can’t call ExecuteScript until the DocumentLoaded event has been fired. Another huge difference with the Edge WebView control is that it does not have a non-async version of ExecuteScript so we pump the message loop while we wait for it to complete. This approach works most of the time but can have issues. Ideally if you change all of your code to use WebView.ExecuteScriptAsync() instead, it might get …

So, @curtisw is there a backward compatible way to do this? ExecuteScriptAsync() doesn’t seem to exist for the RH7 version of Eto.

For context what’s happening here is the html page starts to navigate to a bogus page with href = 'rhinosignal....' after a user interaction. In Rhino there’s a custom OnLoading() handler written to intercept that, stop navigating (WebViewLoadingEventArgs.Cancel=true), do some stuff and finally call the ExecuteScript() to reflect certain changes on the html page/UI. Works perfectly fine in RH7 so far. No luck in RH8, as mentioned earlier in the above linked thread.

[curtisw (Curtis Wensley)]

Hi @Will_Wang,

One thing that might work would be to use Application.Instance.AsyncInvoke(() => ExecuteScript(...)) during the loading event, so it schedules the script to execute on the next message loop.

Another would be to have a different version of your plugin for Rhino 8 which uses ExecuteScriptAsync() instead, which should avoid any deadlock situation.

Hope this helps!