User pmcpa reported a UI bug on mobile foldable devices (specifically Samsung Fold) following the v2026.2.0-latest update. The issue manifests on the homepage where thread content is restricted to the left half of the screen when the device is unfolded, while headers and footers remain full-width. This problem was observed on two self-hosted sites but not on the public Meta forum. pmcpa noted that the layout corrects itself once a user navigates into a specific thread.
After pmcpa confirmed the issue persists in safe mode, NateDhaliwal hypothesized it relates to recent changes in how Discourse decides between desktop and mobile views based on viewport size. supermathie tested on a OnePlus Open and did not reproduce the error, suggesting a configuration difference. chapoi moved the topic to the UX category, suspecting a media query conflict.
When pmcpa offered to share private site credentials for debugging, supermathie clarified that individual support via PM is reserved for hosting customers. Staff member Don identified the root cause: a conflict between the new viewport-based style and the legacy mobile view, caused by the “Viewport based mobile mode” site setting being disabled. Don advised enabling this setting to resolve the layout issue. pmcpa agreed to test the fix, expressing concern about potential side effects based on a previous report from October.
v2026.2.0-latest +1 seems to have introduced (at least for my installs) that mobile rendering only shows threads and content on half (left half) of the screen when foldable is “wide”
Header, footer, and column headers (“topic replies, views activity”) are all full width
Tested across 2 sites, same results. Not an issue here on meta.
Same issue if loaded while folded or unfolded
MAY NOT have been 2026.2.0, I only update once a week
Edit, Changed category from Support to Bug
have you tried in safe mode?
Good question, I had not.
I now have, same issue
(Firefox and Chrome, android current builds)
This might have to do with the changes to deciding desktop/mobile views based on viewport size 
.
i know a certain staff member who has a foldable mobile who can test this - i will attempt to summon them…
There was another topic about the change to choose mode based on screen width instead of the separate mobile mode a while back:
Moved this to UX as it’s functional, just not optimal.
The elements are probably using a different (type of) media query.
I don’t have a foldable so might be more tricky to test/repro than to fix. @Falco Don’t you? If so, ping me for a CSS collab xD
@pmcpa also said that it’s not a problem here
Correct, no problem here on meta, problems on self hosted (2x sites I run). Samsung fold
Update to add, once on a thread all is normal.
The best thing to do is share your site URL so people can take a look.
If you don’t want to do that, you can try disabling customisations until it works.
Send me a pm and I will be happy to
We do not provide individual support in PMs, sorry. That’s reserved for our hosting customers.
I can understand that you don’t want to share your forum publicly. Maybe you can find another forum with the same problem on https://discover.discourse.com/ and share that.
You can also try the different themes here on Meta and on try.discourse.org. Though, since safe mode didn’t help, it doesn’t seem that likely it will help.
Perhaps that is the change that caused the problem. Is that within the week between your updates?
https://github.com/discourse/discourse/commit/1880ad8e74df4848a30096ea8b316a1654f3c797
Hello 
The issue you’re seeing is caused by a conflict between the new viewport-based style and the old mobile view. It looks like the Viewport based mobile mode site setting is currently disabled in your admin.
To fix this, simply enable the setting under your site settings. This should resolve the layout conflict.
I didn’t ask for support via PM, I asked to send you the URL and login info as one of the sites is non public and requires login to view.
Thanks though
I’ll give this a try. Hopefully this does not re-introduce the error I reported back in October
