Column resizing gone amok

[Fl1pp3d0ff]

Steps to reproduce the problem

1. Go to a glitch-soc mastodon instance on any web browser
2. Login
3. Open "Notifications", "Home", and "Federated" columns, leaving the toot entry column and the "Getting Started" column active
4. Observe that the toot entry column gets its width reduced if the browser window isn't wide enough.

Expected behaviour

Toot entry column should have a minimum width set such that the characters remaining and "options" displayed don't shrink.

Actual behaviour

Toot entry column shrinks to cut off the right edge of the column, obscuring the characters remaining count. If the toot extends past a certain length and the scrollbar appears int the edit box, some options are also obscured.

Detailed description

Per the screenshot above, the toot entry colum gets shrunk, even though the "Getting Started" column would be a better candidate for the shrinking.
If I had an ultrawide monitor, I'm certain I could expand the browser window width wide enough to allow the viewing of the whole column, but I do not.

Mastodon instance

mastodon.ai8w.ddns.net, infosec.exchange, and others

Mastodon version

v4.3.0-alpha.5+glitch (updated last Saturday)

Browser name and version

Chrome 126.0.6478.127 (Official Build) (64-bit) (cohort: Stable)

Operating system

Windows 11, Linux (Debian, Fedora, and OpenSuSE)

Technical details

I've been experiencing this issue since the upgrade to Ruby 3.3.3 went live, it persists in 3.3.4. I've tried searching for css or other formatting within the code to propose a solution, but being unfamiliar with the code, I could not find what I was looking for.

[Fl1pp3d0ff]

This issue isn't world-ending, mind... It's simply annoying, and really rides my OCD.
The instance (mastodon.ai8w.ddns.net) is running on Debian 12. Other instances running glitch-soc have the same issue (infosec.exchange, for example) but I do not have information on which OS they're running - I don't believe this to be a server OS issue.
I've been able to reproduce this issue in Firefox on Linux and Windows as well.
The OS the browser runs on has no effect on the issue. (and I wouldn't expect it to...)

[Fl1pp3d0ff]

Updated again this morning to all the latest and greatest. Issue persists.