Hacker News Reader

Comment by pjmlp | Hacker News Reader

Not really it is a bit more subtle than that, unless you do some magic incantations with CSS, like z-ordering or transforms, it may bet that software rendering is used instead.

There are a couple of talks regarding CSS tricks to force GPU redrawing.

View on HN

I think that was the case several years ago but I thought these days much more of the browser rendering pipeline was automatically GPU accelerated. It's hard to find up-to-date references (would appreciate any links) but for example going to chrome://gpu shows it using GPU acceleration for both compositing and rasterization (including "multiple raster threads"), as well as the usual suspects like video decoding, canvas and WebGL.

Don't be fooled by canvas/WebGL support.

I remember seeing this kind of content on Google IO and WebDev talks.

Would need to also go treasure hunting to find them.

Treasure hunting to find an API widely supported on 95%+ of devices?

Treasure hunting the Google IO/WebDev talks about the CSS magic incantations that force GPU rendering.

Here is an old article,

https://www.chromium.org/developers/design-documents/gpu-acc...

Do we know for sure if this is still true in modern browsers?

Browser makers are constantly updating their rendering engines and these pieces of wisdom do go out of date so it's important to verify them every few years.

As answered on sibling comment I remember seeing this on Google talks, not sure about latest versions without going hunting for this information.

Reply on news.ycombinator.com