|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
Hi,
I just wanted to report that I upgraded to 22.0.30 and it seems the control constantly locks up (not taking any mouse or keyboard input). Hovering the mouse over links seems to indicate the mouse over effects but clicks or scroll doesn't work. Also the whole (WinForms) application which hosts the browser doesn't respond to any mouse or keyboard event.
I have to go back to 21.3.18 in order to make it work.
Regards,
Stefan
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
If you have a simple test app please send it over and we will investigate this immediately. We did change how event routing works in this build but our internal test did not notice the issue.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
I figured out that the way I handled focus management in the previous version of the browser controls breaks it. I handled the "GotFocus" event and ensured the browser gets the input focus. I also have code like this in place:
BeginInvoke(new MethodInvoker(() =>
{
WebControl?.Focus();
WebControl?.WebView?.SetFocus();
}));
This code focused the web view in the previous version.
I now have to remove the GotFocus event in order to prevent the lockups but I'm not longer able to move the input focus to the web view using the method above. What is the preferred (new?) way to focus the web view?
Regards,
Stefan
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
It seems calling
WebControl?.Focus();
(without BeginInvoke) does the trick. Can you confirm this is the correct method to move input focus to the web view?
Thanks,
Stefan
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
Yes. It is no longer necessary to use BeginInvoke to delay the call in this build. However we are not aware that BeginInvoke would break things. So if you can put a test project and send it over we would investigate it as soon as possible.
You should definitely NOT call focus both on the WebControl and on the WebView. If you use WebControl, you should ONLY call Focus on WebControl. WebControl internally calls WebView.Focus with different arguments so calling WebView.Focus immediately after would change expected behavior from WebControl.Focus.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
I think it was a combination of the way I handled focus previously with the handling of the GotFocus event. Removing the GotFocus handling completely and calling only WebControl.Focus() seems to resolve all issues.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Great to hear that! Please feel free to let us know if you run into anything else.
|
|