I wish field-sizing had better browser support so that we could drop JS hacks.

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: hbhalodia <hbhalodia@git.wordpress.org>
Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

I think rebasing went bit crazy 😅

I think rebasing went bit crazy 😅

Yeah, I noticed. oops, not sure what happened! I'm going back to my usual pattern of merging trunk until I figure that out. I was just asking you about it in the other thread.

I think rebasing went bit crazy 😅

Fixed the branch, ready for review again @Mamaduka.

Did you figure out what the reason was?

@Mamaduka I think what happened is I was resolving conflicts when rebasing on trunk, then inadvertently pushed the branch while still in the unresolved state. To fix the issue I aborted the rebase, did the rebase again completing it this time and force pushed.