Chrome 157 ships a shorthand for rounded and squircle corners
A new corner property, and per-corner variants like corner-top-left, set border-radius and corner-shape together in one declaration instead of two.
Tagged
The parent selector we asked for since 2003 has been shipping for years now. It does not just save a class name. It moves state out of JavaScript entirely.
Media queries ask how big the window is. That was never the question. Components care about the space they are given, and now they can ask.
Animating between two states used to mean keeping both in the DOM and choreographing them by hand. The browser will now do the hard part for you, in about six lines.
A new corner property, and per-corner variants like corner-top-left, set border-radius and corner-shape together in one declaration instead of two.
WebKit now automatically rewrites light-themed sites into dark mode for users who want it, preserving contrast and letting developers opt out with one CSS declaration.
The property finally takes a custom string instead of the default ellipsis when text is clipped, something Firefox has supported since 2011.
WebKit's release also adds a ::field-content pseudo-element for Customizable Select, and renames the Grid Lanes flow-tolerance property to fit-tolerance.
Firefox was the last major browser holding this behind a flag. With 159 out, animation-timeline works without JavaScript everywhere that matters.
WebKit adds the device-posture media query and a Viewport Segments API behind feature flags, letting web pages detect and lay out around a fold for the first time.
The random() function generates a number directly inside a property value and can share results across elements and properties. Chrome is the first browser to support it.
Dividing two CSS values of the same type now returns a plain unitless number in Firefox too, matching Chrome and Safari, which already shipped it.
WebKit has started shipping interpolate-size and calc-size(), the CSS pair that lets you animate height: auto without JavaScript, two years after Chrome did.
Unlike :invalid, it waits until the user has interacted with the field, so empty required inputs stop turning red before anyone has typed anything.
Baseline turns "which browsers support this" into a yes or a no, and it is now built into MDN, the docs, and a linter you can run in CI.