We have been testing EO 22.0.68 using the TabbedBrowser on a recently patched 21H2 Windows 10 machine with a touchscreen.

To test, we load a simple web page with nothing more than an input box (i.e. we navigate to "file://D:/index.html" and have an index.html which contains nothing more than <input type="text">).

We run our tests with TabbedBrowser maximized (i.e. using the square in the top right corner, next to the X).

Step 1) Click in the input box
- The input box takes focus
- Windows resizes TabbedBrowser (to give space to the on-screen keyboard). You can see this occurring as the "Ready" in the bottom left corner jumps up above the keyboard
- The on-screen keyboard appears

Step 2) Click out of the input box (somewhere else on the web page)
- The input box loses focus
- Windows resizes TabbedBrowser (to fill the screen again, leaving the Start Menu/Taskbar at the bottom of the screen)
- The on-screen keyboard disappears

So far, so good.

However, if between Step 1 and Step 2, we type a letter using the on-screen keyboard (so it appears in the input box), when we do Step 2, the focus is removed from the input box but the keyboard stays on screen. The only way to get the keyboard to hide is then to give focus to the input box again and click out of it again. It seems to do this reliably (i.e. ever time we try).

It sometimes does this without entering a letter using the on-screen keyboard (i.e. just clicking in and then out of the input box), but not every time.

We've tried using Chrome (we have a copy with a version of 96.0.4664.45), and it behaves as expected and hides the on-screen keyboard in all cases when the focus is removed from the input box.

We think this behavior may have changed in a cumulative update late last year. We have a Windows 10 21H2 device that was patched prior to November and it isn't behaving this way, but all devices that are recently patched show the broken behavior.

Thanks for the update, much appreciated. Any idea when the new release is likely to be (i.e. days/weeks/months)?

Hi,

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

Thanks!

Great. Thanks for confirming the fix!