tag:tenfourfox.tenderapp.com,2012-01-07:/discussions/problems/7470-modernizr-considers-tff-to-be-a-touch-deviceTenFourFox: Discussion 2015-11-03T14:00:43Ztag:tenfourfox.tenderapp.com,2012-01-07:Comment/383555632015-11-02T15:48:46Z2015-11-03T08:10:13ZModernizr considers TFF to be a touch device<div><p>Ups, there was a typo in my email address …</p></div>funtooshtag:tenfourfox.tenderapp.com,2012-01-07:Comment/383555632015-11-02T15:53:46Z2015-11-03T08:10:13ZModernizr considers TFF to be a touch device<div><p>Okay, I changed dom.w3c_touch_events.enabled in about:config
from 1 to 0, problem solved. Not sure whether the default was 1 or
not.</p></div>funtooshtag:tenfourfox.tenderapp.com,2012-01-07:Comment/383555632015-11-02T16:08:46Z2015-11-03T08:10:14ZModernizr considers TFF to be a touch device<div><p>One more (and hopefully final) follow-up just to close the
issue, it appears that in some (if not all) versions of FF the flip
of the touch simulator switch in dev tools changes
dom.w3c_touch_events.enabled to 1, as it should, but without
resetting it when un-checking the button or restarting FF.<br>
Sorry for the confusion!</p></div>funtooshtag:tenfourfox.tenderapp.com,2012-01-07:Comment/383555632015-11-03T14:00:42Z2015-11-03T14:00:42ZModernizr considers TFF to be a touch device<div><p>Yes, we didn't make any change of that sort, but good to know
you discovered why. Glad it is functioning as you expect now.</p></div>Cameron Kaiser