Microsoft Is Improving Touch Performance In Project Spartan Web Browser By Removing The 300ms Tap Delay

Project Spartan Imaeg

Microsoft today announced that W3C has published Pointer Events as a final Recommendation standard. Microsoft has made Improvements for  included better extensibility for new device types, additional configuration values for scrolling and zooming behavior, event constructors for synthesizing custom pointer events, and more. Apart from Pointer Events, Microsoft is also making additional improvements for touch interoperability in the new rendering engine for Project Spartan.

To make sites designed for a big monitors work on a tiny screen, mobile browsers scaled Web pages in a to make it fit better. The double-tap gesture was then introduced to quickly zoom in and out of relevant content. There is a trade off in this method.

From the perspective of a gesture recognizer, any single tap could be followed by another making it a double-tap instead. So before committing to the action of a tap (e.g. navigating a link or clicking a button), the browser must pause for a moment to see if another tap is right behind it. This introduces a noticeable delay (300ms) when you’re just tapping to activate something. This problem has been well documented and many fixes or workarounds have been proposed, including the popular FastClick library and others.

Additionally in IE11, if you disable zoom altogether in your viewport rule (e.g. user-scalable: no) then this also disables the 300ms delay.

Now in the new engine, setting a viewport rule with a width less than or equal to the device-width (a strong signal that you’re not a desktop site we need to optimize for small screens) will also disable the 300ms delay. This results in significant performance wins for mobile sites.

Learn more about it here.

Some links in the article may not be viewable as you are using an AdBlocker. Please add us to your whitelist to enable the website to function properly.