The image below is a screenshot from a post I was writing on users.rust-lang.org.
As is pretty plain to see, the input field is just completely broken. And it’s not new, it’s been going on for quite a while.
Oddly enough, meta.discourse.org doesn’t seem to have that problem. So what could be causing the issue?
For some reason the restrictions prevent me from posting the actual image in OP. Which is pretty counterproductive I have to say.
How will you know what I mean if I can’t post a single image showing the problem?
Anyway, I’m allowed to do it here in a separate post, so here it is:
Hi @jjpe 
welcome 
Can you provide more information about what device and OS that is please?
I cannot reproduce this. I was just on the Rust forum myself on both my iphone 15 pro iOS 18.0.1 and my Macbook MacOS 15.01 Sequoia and the composer is working as expected.
If it is only happening on that forum, I would think it is a theme component or plugin issue that your device / browser may not like. 
you could maybe give safe mode a try.
HI, thank you
Sure, it’s an android Samsung phone. AFAIK they all run the same software, aside from drivers.
It’s important to note that I only have the issue with my phone. The problem does not appear on my other devices (laptop, desktop).
I’ll give that a try, but it wouldn’t be a solution if it resets the color scheme to white. Not a big fan of being blinded
Ok so safe mode does seem to have nonzero effect.
However it’s difficult to gauge as the issue doesn’t occur 100% of the time. So the best thing for now I think is to use the site on safe mode for a while, and see if the issue pops up at all.
If it doesn’t then that’s a clear direction to look into: a component or plugin.
It turns out to be more complex than some plugin or component causing the issue.
The screenshot below is from internals.rust-lang.org with safe mode enabled.
Yet the text box is still sized wrong.
what model and os version? we need to be able to reproduce this to figure it out.
And which browser?
That would be the chrome browser.
The only accessibility setting I have enabled is “Force enable zoom”, but that shouldn’t be a factor here, since by default it doesn’t do anything. It just allows me to zoom in when otherwise that wouldn’t be possible.
I guess I missed this before.
The phone is a Samsung Galaxy S24+ with the latest updates installed.
That is, Android 14 and OneUI 6.1
I’m cross-linking a post I made about this issue on users.rust-lang.org.
More than a month later, has anything been done about this?
We’ve seen this before. Usually Font size and Display size settings on device.
It’s just web output. Check all influences on your Chrome display.
See the discussion here:
Yeah the thing is, there are none if we’re talking about the browser. That’s just chrome for android, which has no support for eg extensions or plugins. So I also double-checked the accessibility settings, in particular text zoom. All set to the default values.
Meanwhile I’ve also encountered the problem on the KDE discourse, so it’s definitely an issue with discourse itself.
Strangely, responding here on meta doesn’t exhibit this problem.
But it is a problem, and one that needs solving because it just breaks the UX.
Basically it is same that has bothered Safari/iPadOS long time now. The main reason why I don’t use Safari for Discourses any more, only the Hub or PWA.
But the most annoying thing is it is not constant. But it happens really often.
Any of my android users haven’t complaint about that, though. And I think quite big deal of those users has a Samsung — it has quite good market share in Finland.
Using the sites as a PWA does seem to help.
But that is little more than a workaround of course - PWA’s are still web apps. It’s right in the name. And as such, they still run in a browser, just without the browser chrome (eg address bar).
So perhaps that could play into this issue? Perhaps some height property isn’t calculated properly in a browser that has actual browser chrome?
Completely random curiosity question, does using a different app as your keyboard app change anything by chance?
Honestly I don’t know. No alternative to SwiftKey is acceptable for serious usage to me (I’ve tried - all alternatives just suck, or perhaps I just can’t get used to them, including GBoard), so it’s a bit of a moot point.
I’m just curious if it’s somehow the keyboard and browser combo causing issues, if you temporarily use something else, does the issue persist?
I just tried that.
Annoyingly, I cannot reproduce it right now, on any of the discourse deployments. That is to say, they currently all behave like I expect they would.
I did get a system update a couple of days ago, and I’m thinking that among the changes is something that’s relevant to this issue.
While I cannot be 100% sure, if true the bug would be in the Chrome engine code or Android code somewhere rather than in discourse itself.
