Support Request: Buttons on Metro IE Browser Skin require multiple touches to activate

Description

We have installed and configured Sitekiosk 8.9 on Windows 8.1/IE11 using Start Screen and Metro IE skin via an NEX touch screen. The standard browser buttons (refresh, print, logout, close etc). Sometimes (infrequently) work on a single touch, but most often require multiple touches (2 to 6) to work. Most often, on first touch, the background of the buttons turns grey (same behaviour as on hover of mouse pointer). Another touch soon after the first will often activate the function. but sometimes it requires multiple further touches. So, it can require up to six touches of the close button to close the browser window. This is annoying and inconvenient for customers using the kiosk. Can you offer any suggestions?

Answer: (2)

Re: Buttons on Metro IE Browser Skin require multiple touches to activate 1/5/2015 5:24 PM
- Are you able to replicate the issue using any of the other skins/browser templates in the SiteKiosk configuration?
- Is the behavior the same when starting SiteKiosk in Start Once mode vs. Autostart mode?
- Are you able to replicate the issue on more than one machine with SiteKiosk installed?

There are no known issues with the touch feature of the Windows OS and the skins in SiteKiosk, as the behavior should be the same as that of a "mouse click"... You may try updating or re-installing the drivers responsible for the touch feature of your monitor to see if there is a change in behavior, as it seems this may be an isolated issue.
Re: Buttons on Metro IE Browser Skin require multiple touches to activate 1/5/2015 10:56 PM
I will test the scenarios you have suggested and report back. From my reading, IE11 on Windows 8.1 brought a new feature with it - the ability to simulate the hover feature on a touch screen via a single touch. We wondered if this feature might be interfering with the functioning of these buttons. But if you have other customers using IE11 on Windows 8.1 who have not reported the same problem, then this would could point to an issue with our particular configuration.
My Account
Login
Language (Tickets):