No bundle size changes

Generated by 🚫 dangerJS against 6b146ef

I didn't have the bandwidth to handle the breaking change at that point. So I went with the simplest changes.

But why roll this breaking change out partially? We never do this. Especially because it leaves code in an inconsistent state where we still use the old prop but also the new prop. Why is this change necessary?

@eps1lon The current changes aren't breaking, It's meant to apply changes that should have come from the time we introduced the new preferred implementation (CSS over the previous JS measuring approach).

My hope is that these changes will allow to makes the future breaking change PR more focused on removing the previous legacy implementation.

I have updated #20012 to include #22799. Hopefully, it will be an easy one to handle.

The current changes aren't breaking, It's meant to apply changes that should have come from the time we introduced the new preferred implementation (CSS over the previous JS measuring approach).

But they do change tests which is a clear indication of a breaking change.

Will revert the test changes in a follow-up since this was accidentally merged.

But they do change tests which is a clear indication of a breaking change.

The tests switch to the non legacy implementation. This implementation was untested even though we were depending on it. I believe it should have been done a long time ago.