Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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
UA string changes
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:
Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Trident/6.0; Touch)
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:
Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0)
For more info, see User-agent string.
DOM events
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:
Gesture events:
Manipulation state event:
CSS properties
Internet Explorer 10 on Windows 7 doesn't support these Cascading Style Sheets (CSS) properties:
Scrolling properties:
- -ms-overflow-style
- -ms-scroll-chaining
- -ms-scroll-limit
- -ms-scroll-limit-x-max
- -ms-scroll-limit-x-min
- -ms-scroll-limit-y-max
- -ms-scroll-limit-y-min
- -ms-scroll-rails
- -ms-scroll-translation
Zooming properties:
- -ms-content-zoom-chaining
- -msContentZoomFactor
- -ms-content-zooming
- -ms-content-zoom-limit
- -ms-content-zoom-limit-max
- -ms-content-zoom-limit-min
Touch behavior property:
Scroll snap points properties:
- -ms-scroll-snap-points-x
- -ms-scroll-snap-points-y
- -ms-scroll-snap-type
- -ms-scroll-snap-x
- -ms-scroll-snap-y
Zooming snap points properties:
DOM 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.
Simulating hover on touch-enabled devices
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.