Hi,
We have looked into this and indeed found a problem with StopLoad. This will be fixed in our next build. However regardless you can not use StopLoad to break WaitOne. This is because all commands to the browser engine are sent in a single sequence, so one won't be sent (and processed) until the other one is done. This means the StopLoad command will not be processed until WaitOne returns.
If you must trigger some action after the load has been stopped, you can do it this way:
Code: C#
webView1.LoadUrl(strURL).OnDone(()=>
{
//do something after the task has completed or been canceled
});
Note that even this code will have problem in the following sequence one after another immediately:
1. Create the new WebView;
2. LoadUrl;
3. StopLoad;
This is the issue that we have found and will be fixed in our next build. In a "normal" scenario such as the following it would work OK:
1. Application starts, UI initialize and WebView is created;
2. User enters a Url or press a button to load the Url;
3. User press another button to call StopLoad;
We will reply here again once a new build with the fix is posted.
Thanks!