Animating CSS width or height no longer force a Main Thread animation (in Chrome, under the right conditions)

Chrome 144 introduces a performance optimization where width and height animations no longer force execution on the Main Thread if these values don't actually change during the animation. This particularly benefits View Transitions, where ::view-transition-group pseudos often have static width/height keyframes that can now run on the Compositor. The Blink engine now intelligently checks whether width/height values actually change across keyframes, including handling implicit keyframes and keywords like 'auto'. For animations where dimensions do change, developers can still optimize by converting width/height animations to scale transforms, either manually or using frameworks like Motion.