Google To Solve The Scrolling Problem Using Microsoft’s Pointer Events API
Although, Google’s Chrome browser is the most preferred browser courtesy its great development tools but it is undeniable that there are certain palpable issues with it. One of such issues is the lagged scrolling offered by Chrome. It is no secret that Chrome has the most scrolling issues as compared to its counterparts Firefox, Safari etc. However, the good news is that Chrome has finally decided to address this scrolling issue for both mouse scrolling and touch scrolling across all platforms.
To solve the problem, Chrome will use the Pointer Events API. Pointer Events is something that Microsoft had started using with the now almost-obsolete Internet Explorer. However, Chrome had always shunned the idea of using Pointer Events and instead decided to go ahead with the ‘Touch Events’ which is what Apple uses for its Safari browser. Pointer Events became a W3C standard recently back in February. Speculations are that the standardisation is something that provoked Google to adopt Pointer Events.
Till now, the Touch and Mouse interactions were handled separately by the Chrome browser. However, the Pointer Events API is something that combines Touch and Mouse interactions into a single, unified set thus providing smoother scrolling and hence major advantages to both the users and web developers. For more technical details about the Pointer Events API, please have a look at the source mentioned below.
Despite the plans to shift to Pointer Events, Google is saying that they do not expect the Touch Events to go away completely in the future. With the Internet Explorer adding #-Link-Snipped-#, Google is confident that it is possible to combine both Pointer and Touch Events without affecting the web compact. Although a stable release using Pointer Events might take some time, the good news is that the feature will be supported across all operating systems.
Source: <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ODWmcKNQl0I" target="_blank" rel="nofollow noopener noreferrer">Redirecting to Google Groups</a> | Via: #-Link-Snipped-#
To solve the problem, Chrome will use the Pointer Events API. Pointer Events is something that Microsoft had started using with the now almost-obsolete Internet Explorer. However, Chrome had always shunned the idea of using Pointer Events and instead decided to go ahead with the ‘Touch Events’ which is what Apple uses for its Safari browser. Pointer Events became a W3C standard recently back in February. Speculations are that the standardisation is something that provoked Google to adopt Pointer Events.
Till now, the Touch and Mouse interactions were handled separately by the Chrome browser. However, the Pointer Events API is something that combines Touch and Mouse interactions into a single, unified set thus providing smoother scrolling and hence major advantages to both the users and web developers. For more technical details about the Pointer Events API, please have a look at the source mentioned below.
Despite the plans to shift to Pointer Events, Google is saying that they do not expect the Touch Events to go away completely in the future. With the Internet Explorer adding #-Link-Snipped-#, Google is confident that it is possible to combine both Pointer and Touch Events without affecting the web compact. Although a stable release using Pointer Events might take some time, the good news is that the feature will be supported across all operating systems.
Source: <a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ODWmcKNQl0I" target="_blank" rel="nofollow noopener noreferrer">Redirecting to Google Groups</a> | Via: #-Link-Snipped-#
0