Split input doesn't scale down when Chatterino scales down

[pajlada]

Checklist

• I'm reporting a problem with Chatterino
• I've verified that I'm running the most recent nightly build or stable release
• I've looked for my problem on the wiki
• I've searched the issues and pull requests for similar looking reports

Describe your issue

When zooming in & out of Chatterino, the height of the split input will change with it. Sometimes when doing this, the height will not change. Might be related to having multiple tabs open.
I don't have clear reproduction steps

Screenshots

No response

OS and Chatterino Version

Chatterino 2.5.1 DEBUG (commit 6f489b7 modified) built with Qt 6.7.0 Running on Arch Linux, kernel: 6.8.9-arch1-1

[Mm2PL]

Might happen when changing DPI (xrandr --output $YOUROUTPUT --dpi 500). I think I've seen this happen when messing with DPI settings

[4rneee]

For me the placeholder text in the split input (i.e. "Send message as xyz...") does not scale when zooming in/out until switching to a different tab.
This might be a different issue and I can create one if you would like me to.

After taking a look at the code I am not sure if this might be a issue with QT as you set the font for the textEdit widget:

chatterino2/src/widgets/splits/SplitInput.cpp

Lines 236 to 237 in bdd903b

	this->ui_.textEdit->setFont(
	app->getFonts()->getFont(FontStyle::ChatMedium, scale));

which works for the plain text but not the placeholder.

[pajlada]

For me the placeholder text in the split input (i.e. "Send message as xyz...") does not scale when zooming in/out until switching to a different tab. This might be a different issue and I can create one if you would like me to.

After taking a look at the code I am not sure if this might be a issue with QT as you set the font for the textEdit widget:

chatterino2/src/widgets/splits/SplitInput.cpp

Lines 236 to 237 in bdd903b
this->ui_.textEdit->setFont(
app->getFonts()->getFont(FontStyle::ChatMedium, scale));

which works for the plain text but not the placeholder.

It's a semi-related issue, but it's not quite the same as my issue. Nerixyz has fixed this in #5960