Logo
My Account |  Site Map | Contact Us  
Welcome Guest Search | Active Topics | Sign In | Register

20.1.88 onscreen keyboard doesn't show when an input box already has focus Options
JW
Posted: Thursday, July 16, 2020 8:52:53 AM
Rank: Member
Groups: Member

Joined: 2/8/2019
Posts: 18
Using the latest release (20.1.88) the onscreen keyboard is no longer displayed when pressing on an input box that already has the focus.

This can seen using TabbedBrowser by:
1 - navigate to www.google.com
2 - press in the "search" box
3 - wait for the onscreen keyboard to be displayed
4 - press the X on the onscreen keyboard to close it (in the top right of the keyboard)
5 - press in the "search" box again (while it still retains focus).
6 - nothing happens

Using the previous release (20.1.45) the keyboard would have been displayed.

If you move the focus and press on the input the keyboard is displayed, so its something to do with it already having the focus.

We've tested this on various touchscreen devices running various versions of Windows 10.

I'm assuming something has changed Chromium-side in the move to v81 (from v77)?
eo_support
Posted: Monday, July 20, 2020 3:58:13 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,331
Hi,

This is just to let you know that we are able to reproduce the problem but we are still trying to find the root cause. We will reply here again as soon as we have an update.

Thanks!
eo_support
Posted: Monday, July 27, 2020 3:29:59 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,331
Hi,

This is just to let you know that we have posted a new build that should resolve this issue. You can download the new build from our download page. Please take a look and let us know how it goes.

Thanks!
JW
Posted: Monday, August 3, 2020 4:55:20 AM
Rank: Member
Groups: Member

Joined: 2/8/2019
Posts: 18
Hi,

I can confirm this fixes the issue. Out of interest, are there any details as to what the bug was?

Thanks.
eo_support
Posted: Monday, August 3, 2020 10:08:33 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,331
Hi,

The root of the issue is a Windows API that triggers a callback when the virtual keyboard has been closed is failing in our code. We do not know exactly why it fails since the Windows API is a black box that we can not debug into. Our guess is Windows checks whether the callback's address is within a valid physical DLL's address space and ignores it when it is not. Since in our code the entire browser engine's code is loaded from memory, not from a physical unmanaged DLL, it would fail this check thus trigger the issue. We have changed our code not to rely on this callback so it should work now.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.