pmcpa
(pmcpa)
29 בינואר, 2026, 1:40am
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)
29 בינואר, 2026, 1:44am
2
Edit, Changed category from Support to Bug
Lilly
29 בינואר, 2026, 1:51am
3
have you tried in safe mode ?
2 לייקים
pmcpa
(pmcpa)
29 בינואר, 2026, 1:55am
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
29 בינואר, 2026, 6:08am
6
i know a certain staff member who has a foldable mobile who can test this - i will attempt to summon them…
Moin
29 בינואר, 2026, 6:39am
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?
chapoi
29 בינואר, 2026, 7:04am
8
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
supermathie
(Michael Brown)
29 בינואר, 2026, 11:57pm
11
Here is what I see on my OnePlus Open:
Everything looks good to me.
לייק 1
Moin
30 בינואר, 2026, 12:06am
12
@pmcpa also said that it’s not a problem here
2 לייקים
pmcpa
(pmcpa)
30 בינואר, 2026, 12:55am
13
Correct, no problem here on meta, problems on self hosted (2x sites I run). Samsung fold
pmcpa
(pmcpa)
30 בינואר, 2026, 1:06am
14
Update to add, once on a thread all is normal.
supermathie
(Michael Brown)
30 בינואר, 2026, 1:14am
15
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)
30 בינואר, 2026, 1:18am
16
Send me a pm and I will be happy to
supermathie
(Michael Brown)
30 בינואר, 2026, 3:52am
17
We do not provide individual support in PMs, sorry. That’s reserved for our hosting customers.
2 לייקים
Moin
30 בינואר, 2026, 8:14am
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?
committed 04:19PM - 22 Jan 26 UTC
This consolidates the `mobile/topic-list.scss` and
`desktop/topic-list.scss` int… o `common/base/_topic-list.scss` using
breakpoints. I relocated some styles to more relevant files where
possible.
There shouldn't be any significant visual changes as a result, as this
is focused on consolidation.
Don
30 בינואר, 2026, 8:27am
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)
30 בינואר, 2026, 10:05am
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)
30 בינואר, 2026, 10:11am
21
I’ll give this a try. Hopefully this does not re-introduce the error I reported back in October