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

Windows 10 Touch Keyboard doesn't pop up on EO Webbrowser Options
Clarence
Posted: Friday, November 8, 2019 1:44:14 AM
Rank: Newbie
Groups: Member

Joined: 9/29/2019
Posts: 6
Hi,

We had an issue with EO WebBrowser on Windows 10 (1903), exact version 10.0.18362.418 and 449, on Microsoft Surface Pro 5. The issue is like this:

1) Using google chrome (latest version) and go to google.com. Touch on the search bar, the touch keyboard will pop-up
2) Using EO TabbedBrowser sample (EO.Total 2019.2.91.0) and go to google.com. Touch on the search bar, the touch keyboard will not pop-up.

The strange thing is that, we have a batch of surface pros with this problem. They were on version 10.0.18362.418 and we tried updating to 10.0.18362.419 (all latest patches), which didn't solve the problem. We have another batch of machines that is on 10.0.18362.449 (all latest patches), but they don't have this issue.

Secondly, the issue does not happen on textbox with <input type="Password">, i.e. the touch keyboard will pop up for those textboxes.

These are our findings so far, hope it helps to resolve the issue. If you need further information or a video comparing EO Webbrowser to Chrome, do let us know.

We need to resolve this urgently, as we need to deploy the new machines. Do let us know if you have any findings.

Thanks.
eo_support
Posted: Friday, November 8, 2019 10:23:34 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 21,675
Hi,

Windows constantly changes touch keyboard support and it's been quite a challenge to support it. The current version of EO.WebBrowser is based on Chromium V70 which may not contain support for the latest Windows update. We are in the process of refreshing the Chromium version but that may take a while and may not meet your time frame. In the mean time you can try to handle this event:

https://www.essentialobjects.com/doc/eo.webbrowser.webview.focusednodechanged.aspx

This event does not have anything directly to do with touch keyboard, however it does give you a chance to display the touch keyboard yourself. So if you already have code that can display the touch keyboard reliability in your environment, you can call that code conditional inside this event handler based on the focused node type.

Please let us know if that works for you.

Thanks!
Clarence
Posted: Friday, November 8, 2019 10:55:32 AM
Rank: Newbie
Groups: Member

Joined: 9/29/2019
Posts: 6
Hi,

Yes, I have already done a workaround using FocusNodeChanged(), it works, but it is definitely not as good as 'native' detection of editable text field clicks. We have to detect the types of text fields (input, textarea), in order to facilitate this workaround. We need to deploy our solutions soon, so we will probably stick to this workaround first and do an update when EO is updated.

Thanks.
eo_support
Posted: Friday, November 8, 2019 11:13:17 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 21,675
Yes. That would be the best option for now. Thanks for understanding!
Clarence
Posted: Monday, November 11, 2019 1:03:29 AM
Rank: Newbie
Groups: Member

Joined: 9/29/2019
Posts: 6
Is there any estimation on when will the next update be ? Thanks.
eo_support
Posted: Monday, November 11, 2019 8:17:22 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 21,675
It is planned around year end.

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.