Context Navigation

Changes between Version 2 and Version 3 of Ticket #29906, comment 51

v2	v3
3	3	At the core of the issue is: browser APIs will let us detect '''touch events''', but not the presence of a touch screen in and of itself.
4	4
5		Detecting touch events is all well and fine in the mobile context, but we're at a loss to detect a device that runs a standard desktop OS in combination with touch capabilities (think MS Surface, for example). This is okay in most contexts, but such a device with no other ~~input~~ pointing device will basically be out of luck... And there's nothing we can seem to do about it via capability detection.
	5	Detecting touch events is all well and fine in the mobile context, but we're at a loss to detect a device that runs a standard desktop OS in combination with touch capabilities (think MS Surface, for example). This is okay in most contexts, but such a device with no other pointing device will basically be out of luck... And there's nothing we can seem to do about it via capability detection.
6	6
7	7	Modernizr, for example, used to document their touch detection as detecting touch (screens),but they have since moved to clarifying that they also only detect touch events (countless discussions online documenting the same reason as us as to why): see comments at https://github.com/Modernizr/Modernizr/blob/master/feature-detects/touchevents.js#L19