Post has attachment
Chrome is finally shipping smooth scrolling - please stop trying to do it yourself from JavaScript!

Smooth scrolling (animating the scroll position on mouse-wheel click or keyboard press) is one of our oldest open chromium feature requests (http://crbug.com/575). Thanks to +Steve Kobes​​ and Yash Malik, we're now shipping this feature in Chrome 49! See https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/UhE1rxzhkkk/fxUQqTWRDQAJ for details.

A few websites have wanted their users to experience smooth scrolling badly enough that they've relied on a JavaScript library to provide it. Such libraries consume all wheel events and implement their own scrolling animation. Now that all major browsers natively support smooth scrolling, you should no longer depend on these libraries. They have the major disadvantage of being bad for scroll performance (they defeat browser's threaded scrolling optimizations). If that's not enough, we're hoping to fix a bug in blink that old versions of a popular SmoothScroll.js library accidentally depended on, and when we do that any sites still using it will stop scrolling with mouse and keyboard entirely! See http://crbug.com/501568 for details.


Post has attachment

Post has shared content
Some good advice here on measuring scroll performance.
Your application runs buttery smooth on your local machine -- good work! But, how does it perform on your users device out in the real world? To answer that, we need real user measurement (RUM) for RAIL + API's that will help us adapt and optimize the experience at runtime.

Gave a brief talk at the Chrome Dev Summit yesterday with an overview of the various efforts we've been working on to address these needs! Have questions or feedback? Let me know!

Post has attachment
Here's slides from a talk +Philip Jägenstedt and I just gave at BlinkOn about improving interoperability on the web.

Post has shared content
Slides from the State of Blink talk at BlinkOn5, presented by +Sami Kyöstilä, +Rick Byers, and me!

http://bit.ly/blinkon5-keynote

"Variation is creative, it pioneers the advance; standardization is conservational, it seizes the advance and establishes it as an actual concrete fact…. Standardization is thus the liberator that relegates the problems that have already been solved to their proper place, namely to the field of routine, and leaves the creative faculties free for the problems that are still unsolved. Standardization from this point of view is thus an indispensable ally of the creative genius."

Just as insightful as to the most effective use of modern web standards as it was when written nearly a century ago. [Albert Whitney, “The Place of Standardization in Modern Life”, 1924]

Post has attachment

Post has shared content
Great post highlighting the low-friction "pay for play" nature of the modern web.

Post has attachment
Hurray, the UI layer for Chrome Android is finally open source along with the rest of Chrome!

I've argued before (https://plus.google.com/+RickByers/posts/Uq4RR9MuLHs) why I think this is important for the web.

Post has attachment
Chrome supports using hover-capable touchscreens (such as on the Galaxy S4/S5) by triggering :hover styles and mouseover/move/out handlers (just like it does for a stylus or mouse device).

If you have such a device, try enabling this feature at chrome://flags/#enable-touch-hover.  Do you find this useful in practice for navigating websites designed for a mouse, or is it only a gimmick?  Even for sites designed to work well with both touch and mouse, do you like seeing the hover effects with touch?

See http://crbug.com/418188 for details.
Wait while more posts are being loaded