pmcpa
(pmcpa)
1월 29, 2026, 1:40오전
1
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
pmcpa
(pmcpa)
1월 29, 2026, 1:44오전
2
Edit, Changed category from Support to Bug
Lilly
(Lillian )
1월 29, 2026, 1:51오전
3
have you tried in safe mode ?
3개의 좋아요
pmcpa
(pmcpa)
1월 29, 2026, 1:55오전
4
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 .
Lilly
(Lillian )
1월 29, 2026, 6:08오전
6
i know a certain staff member who has a foldable mobile who can test this - i will attempt to summon them…
Moin
1월 29, 2026, 6:39오전
7
There was another topic about the change to choose mode based on screen width instead of the separate mobile mode a while back:
Folding phones is one of the reasons that we made this change. The feedback we’ve received elsewhere is that folding phones should show more on the screen when unfolded. Showing the ‘desktop view’ there is intentional.
Is there a particular part of the UI which didn’t work well when the phone was unfolded?
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
1개의 좋아요
Here is what I see on my OnePlus Open:
Everything looks good to me.
1개의 좋아요
Moin
1월 30, 2026, 12:06오전
12
@pmcpa also said that it’s not a problem here
2개의 좋아요
pmcpa
(pmcpa)
1월 30, 2026, 12:55오전
13
Correct, no problem here on meta, problems on self hosted (2x sites I run). Samsung fold
pmcpa
(pmcpa)
1월 30, 2026, 1:06오전
14
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.
2개의 좋아요
pmcpa
(pmcpa)
1월 30, 2026, 1:18오전
16
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.
2개의 좋아요
Moin
1월 30, 2026, 8:14오전
18
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
Don
1월 30, 2026, 8:27오전
19
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.
3개의 좋아요
pmcpa
(pmcpa)
1월 30, 2026, 10:05오전
20
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
pmcpa
(pmcpa)
1월 30, 2026, 10:11오전
21
I’ll give this a try. Hopefully this does not re-introduce the error I reported back in October