I think that we should aim for the content on individual object pages to fit within the width allocated for the main content column, at least for the first couple sections on each page. This is probably impossible to guarantee for every screen size, but I think we should at least ensure it holds for most browsers at a default zoom on a 1920 x 1080 monitor (the most common resolution).
When it doesn't hold, the content gets pushed further down the page (often off-screen entirely), so at a first glance it looks like the data is missing.
E.g. On some Galois group pages, the "Group action invariants" section appears empty, as everything is pushed down off-screen. We should ideally give a shorter cut-off for wrapping the generators, or be truncated with the full data available as a knowl (e.g. what we often do for displaying very large integers). Checking https://beta.lmfdb.org/GaloisGroup/46T3, here is what I see using Chrome on Windows at default zoom on a 1920 x 1080 screen:
I think that we should aim for the content on individual object pages to fit within the width allocated for the main content column, at least for the first couple sections on each page. This is probably impossible to guarantee for every screen size, but I think we should at least ensure it holds for most browsers at a default zoom on a 1920 x 1080 monitor (the most common resolution).
When it doesn't hold, the content gets pushed further down the page (often off-screen entirely), so at a first glance it looks like the data is missing.
E.g. On some Galois group pages, the "Group action invariants" section appears empty, as everything is pushed down off-screen. We should ideally give a shorter cut-off for wrapping the generators, or be truncated with the full data available as a knowl (e.g. what we often do for displaying very large integers). Checking https://beta.lmfdb.org/GaloisGroup/46T3, here is what I see using Chrome on Windows at default zoom on a 1920 x 1080 screen: