Señors at Scale - Software Engineering & Tech Leadership · Dan Neciu

Modern CSS at Scale with Bramus (Chrome Developer Relations Engineer ,CSS and Web UI, at Google)

·54 min·3 clips

View Transitions can morph a clicked movie poster into the detail page’s larger image and title.

CSS performance starts with the browser. The guest explains that opacity, scale, transform, and translate are usually safer picks when an animation needs to stay smooth. Chromium gets extra attention. Chrome and Edge benefit from shared work in the Chromium project, including hardware acceleration for clip path and background color animations, though the guest says he would want to double-check whether some support still sits behind a flag. Other engines can make different calls. Firefox and Safari may handle the same CSS animation with a different performance profile. Built-in CSS functions come up too. The guest points to light-dark as an example of modern CSS giving developers more expressive tools, while noting that it was specified for colors. The view-transition advice is blunt: do not overdo it. Motion can get distracting, or even physically unpleasant, when too many things move at once. Respect the user. A reduced-motion preference does not have to mean no motion; it can mean using a gentler crossfade instead of sliding content around. Selective animation makes the point. The guest suggests animating only the thumbnail may be enough, without also moving titles, fading descriptions, and capturing every possible element. The host picks up the tradeoff and asks how browser work connects with frameworks like React, Angular, and Vue when platform features have to fit real application stacks. The answer stays practical. Framework adoption depends on the feature, and view transitions are tricky because of browser timings and built-in heuristics. Feedback matters. The guest asks listeners to tell browser DevRel teams what is missing, what hurts, and what the web platform should support next. The episode stays grounded: modern CSS has real power, but browsers, user comfort, and production rough edges still shape the work.

As heard by us

Bramus focuses on browser-specific CSS realities and careful, selective motion.

Bramus stays on browser-specific CSS behavior, starting with the safer motion properties and the hardware-accelerated clip-path and background-color work Chromium browsers have been moving toward.

Read the full review in PlayNext →

Why you'd press play

Browser-specific CSS motion guidance for shipping animations that hold up in real browsers.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Señors at Scale - Software Engineering & Tech Leadership