Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

How to work around issues with tablet PC input service

  • 4 odgovora
  • 2 imaju ovaj problem
  • 1 prikaz
  • Posljednji odgovor od WebTester

more options

On some systems the Tablet PC Input Service is running and it interferes with JavaScript based UI frameworks (jQuery, Kendo). Is there any solution to fixing this issue through code? The alternative would be to tell every user to check for this service to be running and turn it off....which also turns off support for Wacom tablets, smartboards and a bunch of other stuff. Works fine in IE, but also fails in Chrome, so it is not only Firefox. And it is not only one app, there are reports of different browser based apps failing. Any advice is greatly appreciated.

On some systems the Tablet PC Input Service is running and it interferes with JavaScript based UI frameworks (jQuery, Kendo). Is there any solution to fixing this issue through code? The alternative would be to tell every user to check for this service to be running and turn it off....which also turns off support for Wacom tablets, smartboards and a bunch of other stuff. Works fine in IE, but also fails in Chrome, so it is not only Firefox. And it is not only one app, there are reports of different browser based apps failing. Any advice is greatly appreciated.

Svi odgovori (4)

more options

hello, you could try changing the preference dom.w3c_touch_events.enabled in about:config to 1 & see if this is making a difference...

https://developer.mozilla.org/en-US/docs/DOM/Touch_events

more options

Tried this and that did not make any difference. Also tried different systems, one of them with FF4.x (I know, very old) and that didn't even have that setting. Thanks for the reply, it was worth a try.

more options

yes, this setting will only have an effect on firefox 18 & higher. is the same problem also appearing on those systems with the old firefox 4?

a possibly related question was posted here: https://support.mozilla.org/en-US/questions/951632

if you have a reproducible (publicly accessible) testcase for this bug i'd recommend filing a new report at bugzilla.mozilla.org - there it will get the attention of developers, while here on the support forums we're primarily focused on "solvable" issues...

more options

Yes, this also happens on the old version. It is tied most likely to the Tablet PC Input Service. I tried it also with a touch interface and there some stuff works now, but others does not. When using FF with a touch interface I wonder how well that works out. I saw the other post before, but there was no solution given either. The only workaround so far that I found is to stop that Windows service, but then some hardware such as the graphics tablets won't work any longer. One more reason why touch UIs are currently total flops....but that is a different discussion.