|
|
Rank: Advanced Member
Groups: Member
Joined: 10/24/2018
Posts: 97
|
When trying the latest 2020 version in a test system we are seeing threading changes, can you confirm the following?
1. Is WebView.IsLoadingChanged executed on a different thread now?
2. Is WebView.LoadCompleted executed on a different thread now?
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
I also see that LoadFailed is executed on a background thread (not the UI thread). The question is:
1. Is this by design or is this a bug in the current build?
2. What happens when e.UseDefaultMessage() is executed (from the BG thread)
Up until now, I assumed the events are executed on the UI thread.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
As to your questions:
1. IsLoadingChanged. This event should be always called in the UI thread (the thread in which the WebView is created);
2. LoadCompleted/LoadFailed. These two events MAY be called in the IO thread This seems to be an issue. We will look into it and see if we can always trigger these two events in the UI thread;
3. When an Url fails to load, the default error message contains a "hint" message "To customize this message, please handle the WebView's LoadFailed event...." then is followed by the actual error message. e.UseDefaultMessage() turns off this hint message and display ONLY the error message. If you have explicitly set e.ErrorMessage, then e.UserDefaultMessage() has no effect;
Hope this helps.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hello,
This is just to let you know that we have posted a new build that will always fire LoadFailed/LadCompleted in the UI thread. You can download it from our download page and let us know how it goes.
Thanks!
|
|