I believe it's this: https://www.youtube.com/watch?v=w8lm4GV7ahg

There are show notes at the bottom of each slide.

All browsers have had GPU-accelerated rendering in some form for years now. Mobile Safari has had a GPU-accelerated compositor since 2007.

The primary difference between Chrome and Firefox Quantum Render (WebRender) is that Chrome maintains a distinction between painting and compositing, while WebRender mostly collapses the phases into a unified rendering step (and Pathfinder even more so). Everything in Chrome other than media and WebGL goes through a vector graphics API (Skia) before being handed to a compositor that draws tiles on screen. But WebRender renders CSS content directly to the screen, like a game would.

Chrome's had GPU rendering for a while now actually (as has Firefox), those slides were just explaining the basics of how that rendering works.

It already does, there are a couple hack fixes for Safari that force GPU rendering when it otherwise wouldn't.

I thought it was going to be about the Pixel phone and how it lasts or doesn't

Working on pixel phones, "pixel 2018" is a common moniker for pixel 2 before its model name is chosen, relatively late in the product development cycle. Before then it was wahoo or taimen (or other things before directors settle bikesheds).

I though it was going to be either a physical display technology, a Google phone, a Google laptop, or an analytics tracker.