luceos I understand that developers need enough technical information to reproduce an issue, and I’m not expecting anyone to be psychic or to investigate an issue without the necessary details.
However, I think the important point here is that this is not something I’m seeing exclusively on my TV. Other users have also confirmed seeing the same behavior on their TVs, and the discussion itself has now identified several possible factors involving Flarum’s layout, font sizing, scrollbars, and how the blocks respond to different display sizes.
That is why I was reluctant to simply accept that “it’s the TV.” If multiple users can observe the same behavior, while other websites continue to display correctly on those same devices, then I think it is reasonable to at least consider that something in Flarum’s UI or a recent core change could be contributing to it.
I completely understand that reproducing every edge case is difficult, especially with a smaller development team. I’m not asking anyone to immediately fix it; I’m simply pointing out that the issue appears to be broader than one person’s TV, and now that we have identified some possible causes, it may be worth investigating further.
