Bug Report: Bug in onscreen keyboard after pressing escape, no input in browser

Reproduction

On screen keyboard is permantly visible.
When pressing escape, you can enter the password without an issue.
When not entering the password but pressing the X, the keyboard minimizes.
When you maximize the keyboard you can not fill in the text fields in the browser. However the onscreen keyboard shows the keypresses and when sound is enabled you can hear it to.
When taking over the pc with teamviewer and trying to enter text in the text fields it works, when you try the on screen keyboard it works again.

Description

We have sitekiosk configured with chrome as engine to load a website.
On screen keyboard is permantly visible.
When pressing escape, you can enter the password without an issue.
When not entering the password but pressing the X, the keyboard minimizes.
When you maximize the keyboard you can not fill in the text fields in the browser. However the onscreen keyboard shows the keypresses and when sound is enabled you can hear it to.
When taking over the pc with teamviewer and trying to enter text in the text fields it works, when you try the on screen keyboard it works again.
Seems be some focus issue.

Answer: (4)

Re: Bug in onscreen keyboard after pressing escape, no input in browser 4/28/2021 11:00 AM
Hello,

The focus to the input filed on the web page is set through the web page code when the page loads and it loses the focus when the exit dialog was opened. But I was able to use the input field again after clicking once again into the input field on the web page.

Alternatively (if using a mouse) you can use the context menu (right mouse click) to reload the web page.
Or you may lower the idle time (>Screensaver>Idle time before activating the screensaver) to e.g. 60 seconds and start again after the screen saver activation (which reloads the start page

Regards,
Michael Olbrich
Re: Bug in onscreen keyboard after pressing escape, no input in browser 4/28/2021 11:52 AM
Hello,

I also have checked this on a touch screen device and it is reproducible that you cannot write anymore into the input field with the osk after this, also when touching again into an input filed (only with using a mouse it did work).

I will forward it to our developers to check it further.

The only workaround I see is to restart SiteKiosk completely when the exit dialog will be closed.
You may also change the key combination to exit SiteKiosk so that users do not accidentally open the exit dialog with pressing ESC.

Here an example script to restart SiteKiosk after closing the exit dialog.

SiteKiosk.Logfile.OnMessage = OnMessage;
 
function OnMessage(seq, time, utcoff, awtype, awlevel, facility, text){
 	if(text.lastIndexOf("ESC Dialog:Escape Dialog closed") != -1){
     SiteKiosk.Restart();
    }
}


The script checks the SiteKiosk log for the entry that appears when the exit dialog is closed and then restarts SiteKiosk completely.

You can copy & paste it to an editor (e.g. notepad), save it as JS file (e.g. restartOnExitDialogClose.js) to “…\SiteKiosk\Html” and then add it to the SiteKiosk configuration (Start Page & Browser-->Advanced-->Execute script).

Regards,
Michael Olbrich
Re: Bug in onscreen keyboard after pressing escape, no input in browser 5/5/2021 1:51 PM
Sorry for my late response.

I can confirm your workarround is working.

I'm awaiting a final solution.
Re: Bug in onscreen keyboard after pressing escape, no input in browser 5/5/2021 2:11 PM
Hello,

Thank you for your feedback.

As written, our developers will investigate this behavior and fix the issue in a future SiteKiosk version.
Until that happens, maybe also change the key combination to exit SiteKiosk so that the Exit Dialog is not accidentally opened by pressing the ESC key but only if it will be used to exit SiteKiosk.

Regards,
Michael Olbrich
My Account
Login
Search
Search