Internet Explorer 10 on Windows 7
This topic of the Internet Explorer 10 Guide for Developers explains the differences between Internet Explorer 10 running on Windows 7 and Internet Explorer 10 running on Windows 8. All differences involve touch and pen input APIs.
This topic contains the following sections:
- UA string changes
- DOM events
- CSS properties
- DOM properties
- Simulating hover on touch-enabled devices
- Related topics
While Internet Explorer 10 introduces the "Touch" UA string token to identify touch-enabled systems, it's only generated when the user's system is running Windows 8 (or later). For instance, the following UA string will be transmitted on a touch-enabled system running Windows 8:
Internet Explorer 10 on Windows 7 will never report a UA string with the "Touch" token. This is the user-agent string for Internet Explorer 10 running on Windows 7:
For more info, see User-agent string.
Internet Explorer 10 on Windows 7 handles touch and pen input as simulated mouse input for the following Document Object Model (DOM) events:
Internet Explorer 10 on Windows 7 will not fire any of the following DOM events:
Manipulation state event:
Internet Explorer 10 on Windows 7 doesn't support these Cascading Style Sheets (CSS) properties:
Touch behavior property:
Scroll snap points properties:
Zooming snap points properties:
In Internet Explorer 10 on Windows 7, the following DOM touch-related APIs behave differently:
- The msMaxTouchPoints property always returns a value of "0" in Internet Explorer 10 on Windows 7, regardless of the device's capabilities.
- The MSGesture object is undefined.
In Internet Explorer 10 on Windows 8, you can use the aria-haspopup DOM property to simulate mouse hover functionality in touch-based scenarios. You can read more about this behavior in Using aria-haspopup to simulate hover on touch-enabled devices.
This use for aria-haspopup is not supported in Windows 7. Adding "aria-haspopup="true"" to an element doesn't simulate mouse hover in Internet Explorer 10 on Windows 7. However, the aria-haspopup property is still supported for reporting accessibility information to assistive technologies.