Did a quick search and don’t think this has been reported before:
Updated everything and did a rebuild yesterday but since then on the mobile view (chrome latest) at the bottom of a thread the reply button and surrounding furniture is partially hidden:
סיכום מבוסס בינה מלאכותית
A user, WaitroseCarpark, reported that on Chrome mobile, the reply button and related UI elements at the bottom of threads are partially hidden. After testing, they confirmed the issue disappears in safe mode, pointing to a theme conflict. Johani diagnosed the problem: a footer element added via JavaScript in the theme is positioned outside the #main container, interfering with Discourse’s topic-progress widget positioning logic. Johani advised replacing the JavaScript-injected footer with static HTML placed in the theme’s common > footer tab, using this code:
<p style="text-align:center;">
<a href="https://m.do.co/c/06a568f6937f">Hosted using Digital Ocean</a>
</p>
WaitroseCarpark confirmed the fix worked immediately, expressing gratitude for saving them from debugging old CSS. The root cause was theme JavaScript interfering with core layout calculations, resolved by moving the footer content into static theme markup.
Welcome back to Meta @WaitroseCarpark 
I can’t reproduce this issue here. Does it occur if you use safe-mode?
Can you share a link to the site you’re seeing it on?
try this on chrome, mobile
aaaaah safe mode does fix it, looks like the theme. That give me something to think about…
The issue is most likely caused by this element
Notice how it’s outside of the #main element? We use some javascript to position the topic-progress widget that’s based on the difference between the height of the #main div and <body> tag.
This element in your theme is interfering with that.
I’m assuming that the element is added with JavaScript. So, remove whatever JavaScript you’re using to add that and add the HTML directly to your theme if possible.
Add this in the common > footer tab
<p style="text-align:center;">
<a href="https://m.do.co/c/06a568f6937f">Hosted using Digital Ocean</a>
</p>
This should give you the same results without interfering with the topic-progress widget.
Wow, fixed straight away! I was just getting hands dirty with the CSS I did for the theme about 3 years ago, saved me an utter nightmare, thank you so much @Johani !!!