Scrolling slated to improve on your Android device's Chrome browser
Scrolling is going to be smoother on the Chrome browser on your phone and tablet. That is because Google plans on using Microsoft's Pointer Events API and integrating it into the browser. The Pointer Events API allows interactions with the touch and mouse to be seen as a single event (in Chrome they are seen as two separate events) which provides benefits to users and developers.
One major benefit to both is smoother scrolling. Some of the other browsers like Firefox and IE, run smoother than Chrome. The Chromium team listened to feedback from web developers, framework authors, and other browser vendors who said that Pointer Events would be a great addition to the platform. As the Chromium team wrote, "Since we’re committed to a web platform which evolves collaboratively through open discussion and data from real-world development, we need to take this feedback very seriously."
source: Google via Engadget, AndroidCentral
The currently used Touch Events API is not going to disappear, and with IE supporting both, it is possible that Chrome also will continue using Touch Events while starting to implement the Pointer Events API. The bottom line is that Chrome users will soon have a better scrolling experience. This is not going to happen overnight, however. Still, it is something that Chrome users can look forward to.
"Pointer Events offers some technical advantages over the existing use of Touch Events and Mouse Events. Most notably, pointer event listeners never block scrolling, and so replacing all touch event handlers with pointer event handlers will address the main longstanding source of scroll-start jank we see on Android (irrespective of whatever scheduler improvements we’re able to make to better prioritize input handling)...Pointer Events has pretty broad support, but we have some outstanding concerns with the existing API which probably cannot be addressed without a non-trivial breaking change. The key outstanding challenge is to try to identify a design which addresses our concerns without seriously breaking websites which support the existing API. We will of course work closely with the other vendors to try to find a design we can all agree to implement consistently."-Rick Byers, Chromium Team
source: Google via Engadget, AndroidCentral
Things that are NOT allowed: