It looks like when the page loads in portrait mode, the browser fits 3 grid units wide.
After rotating and rotating back, it fits 6, making groups too small to be usable.
The text however is not resized to fit and so titles wrap and values disappear from view.
I have only noticed this today after installing NR 5.0.9, but it might be a well-known and old feature?
NR dashboard is 1.34.0 (same behaviour with 1.32.0)
The same behaviour is seen with Firefox or Chrome on Android.
Both groups are 2x1 grid units.
The page theme is "Compact (32px)"
I haven't seen this problem, though interestingly I do occasionally see a similar thing using Grafana.
If you refresh the page after rotating back does it recover?
You can set the number of columns for different screen widths in the page configuration. Note though that you might not have the number of pixels that you think you have as there seem to be physical and logical pixels on mobile devices, which are often different. Fiddling with those settings should not make a difference to the problem you are seeing though, but it might be worth playing with the numbers to get more info on the problem. I have these settings for the page:
I have the same settings as you, I've never changed these.
It does look like on initial load in portrait it uses the default (3 columns) and rotating back to portrait it switches to tablet settings (6 columns).
But launch the page in landscape and it uses 6 columns.
There must indeed be a virtual vs physical resolution issue here.
According to 1440px.com, the "CSS viewport" is 360 x 780.
If I change the first breakpoint to 768 px and the second to 800, initial load in portrait is 3 columns, rotating to landscape stays at 3 columns (making the landscape page less usable) and rotating back stays at 3 columns (yay!).
Why 768 has this effect when the viewport is 780 remains a mystery.
What does that change to if you rotate and rotate back again?
Mine shows 360x718 and 720x322!
However, as I said, if I change the page settings I cannot seem to get what I expect. More investigation needed, I am reasonably sure that it used to work ok.
Another reason, if one were needed, why modern web UI's should virtually never be using px sizing. A few pixels on a modern screen may be all but invisible and they bear no real comparison with anything usefull.
