in reply to Re^2: Page rendering bugs
in thread Page rendering bugs

The other part of the problem is people front-paging nodes that have haznav problems.

We should just fix 'pre' tags so that they aren't a problem, of course.

I complained to the author about how horrible the table in Inner Scriptorium was. He seemed uninterested in fixing it. I mostly considered it his loss (in keeping his thread rather unreadable; though not to him). Ruining the rendering of an "inner" section is only a little more bothersome. I should put a 'readmore' around the table, though.

- tye        

Replies are listed 'Best First'.
Re^4: Page rendering bugs (haznav)
by jdporter (Paladin) on Jul 14, 2012 at 21:20 UTC
    I complained to the author about how horrible the table in Inner Scriptorium was...

    You said the text in the header row was "huge". I simply used <th><c>. It looks fine for me, in both Firefox and Chrome, as both myself and as Anonymous Monk. So if it looks "horrible" to you, I have to conclude that it's due to something unusual in your setup.

    I should put a 'readmore' around the table, though.

    I should have done that. I have done. Of course, that only removes the "problem" on the section page. I don't know how it affects viewing the node directly, as I have yet to actually see a problem.

    If the "problem" is simply that the table is wide... well, what would anyone do about that? It's a wide table. It has a lot of columns.

    I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.
[reply]
[d/l]
      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.

      - tye        

[reply]

        I do significant restyling as myself, but not as Anonymous Monk, obviously, and afaict it looks fine as Anonymous Monk for me. Does it not for you? I have an alter ego which does not have any custom css. With this user, I cycled through the themes and never saw any problem with the headers being huge.

        My complaint was about the headings being huge. The table is significantly wider due to that.

        I don't know why you are getting that. I have to suppose you have some kind of unfortunate combination of styling that makes it come out that way.

        Oh, wait. Do you have "Large Code Font" enabled? :-)

[reply]
[reply]

In Section Perl Monks Discussion