Yeah, the browser will enable/disable touch support automagically depending on monitor support and what not.
If we're always going to listen to the touch events to enter "touch" mode, we could update TOUCH_ENABLED then, perhaps, in which case, perhaps TOUCH_STATE might be a more appropriate name?