text-box and sibling-count()/sibling-index() are now Baseline, so you can drop the JavaScript workarounds for precise typography and dynamic layouts.
The web.dev August digest moves three features into Baseline's "Newly available" tier: the text-box properties, sibling-count() and sibling-index(), and the autocorrect global HTML attribute. Baseline is the signal you actually care about: a feature now works in every evergreen browser, so you can use it with no polyfill and no support-table lookups.
The two CSS entries are why this tier matters. Firefox 154 completed text-box and the sibling functions on August 18, so all three evergreen engines support them now. Baseline is the settled answer where you used to run a support-table lookup: the cross-engine question is closed, so text-box typography and position-based child styling ship with no polyfill and no feature detect.
autocorrect is the quiet third: a global attribute that now behaves the same across browsers instead of following platform defaults. It sits alongside the CSS pair in this tier, so the form-control behavior you used to assume diverges now has a single cross-browser answer.
The rest of the digest is Chrome-only, so treat it as low priority unless you ship to Chromium. Chrome 152 brings a CSSPseudoElement expansion, alpha(), and window-drag. None of it is part of the Baseline signal, so you can skim it and move on.
Firefox 154 is the last gap: text-box and the sibling functions now work in every major engine, so you can delete the JavaScript and utility-class hacks doing their job.
1 source
Chrome 150 stable ships text-fit, which fits text to its container width in pure CSS and lets you drop FitText-style measurement JavaScript, though the spec stays a W3C draft with no Baseline support yet.
1 source
Firefox 156 now reports `::-webkit-scrollbar` as unsupported in `@supports`, flipping negated feature queries onto standard scrollbar properties, and moves `text-box-trim` onto `::first-line` metrics.
1 source