|The stupid question is the question not asked|
Re^5: Page rendering bugs (wide table)by tye (Sage)
|on Jul 15, 2012 at 00:02 UTC||Need Help??|
It looks fine for me, in both Firefox and Chrome, as both myself and as Anonymous Monk.
That's different than the response I got when I brought it to your attention, which was very close to "It looks fine for me (but I do significant re-styling)". So I stopped worrying about it for the time having been.
If the "problem" is simply that the table is wide...
I think one of the expectations is to be able to read the text of the thread. And I usually will just skip reading if it means I have to scroll a window left and then right for each line of text.
It has a lot of columns.
My complaint was about the headings being huge. The table is significantly wider due to that. It stretches beyond the width of my entire screen, which makes the thread too obnoxious to read.
Even as Anonymous Monk, much of the width of the table is just a waste for the sake of too-wide headings. So, there is much to "do about that" (have wide headings in a row above/below, spanning adjacent columns; split heading into parts so it can wrap; etc.).
well, what would anyone do about that? It's a wide table.
Personally, I'd put the table in a reply inside of a readmore tag. In some ways, 'spoiler' would be even better, except that some people choose 'spoiler' to render as "set text color the same as the background". We should probably add a version of 'spoiler' that forces "click to reload w/ content not missing". BrowserUk would appreciate such (I would think). Maybe call that one "showmore"?
But even with the table columns shrunk down, the table is wide enough that it should be isolated from forcing the whole thread to its width. It would be nice to be able to read the thread even on a somewhat small screen or from a somewhat small windows.