|
|
Rank: Member
Groups: Member
Joined: 9/29/2019
Posts: 13
|
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.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
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.aspxThis 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!
|
|
Rank: Member
Groups: Member
Joined: 9/29/2019
Posts: 13
|
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.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Yes. That would be the best option for now. Thanks for understanding!
|
|
Rank: Member
Groups: Member
Joined: 9/29/2019
Posts: 13
|
Is there any estimation on when will the next update be ? Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
It is planned around year end.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/8/2019
Posts: 57
|
I've just tried the latest release of TabbedBrowser (by installing EO.Total.2020.0.25.0.msi) on two different Windows 10 touchscreen devices (one was v1909, the other v1903). I navigated TabbedBrowser to www.google.com and clicked in the search box in the middle of the page. No on-screen keyboard appeared. I then installed Chrome and did the same, and it the on-screen keyboard appeared on both devices. Is this expected? Was this release meant to behave more like Chrome with regards to the on-screen keyboard? Or is there some setting that I need to be apply? Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
Please navigate to the installation folder and delete eowp.exe (in the same folder as TabbedBrowser.exe) and then run TabbedBrowser.exe again. It should no longer demonstrates the problem.
The root of the issue is in eowp.exe. So when eowp.exe is used it won't work properly. However when eowp.exe is not used (in that case Windows's system file rundll32.exe will be used) the issue should not occur. We will fix eowp.exe in our next build so it will work regardless you use eowp.exe or not.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
We have posted a new build that fixed the issue in eowp.exe regarding touch event. Please download the new build from our download page and let us know if the problem still occurs.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/8/2019
Posts: 57
|
Hi,
The latest release (20.0.33) resolves the issue. The on-screen keyboard now appears as expected when using eowp.exe.
Thanks :)
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Great. Thanks for confirming!
|
|