Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

Re^2: Page rendering bugs

by davido (Archbishop)
on Jul 14, 2012 at 18:16 UTC ( #981839=note: print w/ replies, xml ) Need Help??


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

duplicate perl environments uses <pre> tags, which are a longstanding problem, not just in PerlMonks, but just about everywhere. If it's a big problem you could specify in your CSS that pre blocks should be constrained to a maximum size, and should be scrollable. Twitter Bootstrap offers this CSS option, for example.


Dave


Comment on Re^2: Page rendering bugs
Download Code
Re^3: Page rendering bugs (haznav)
by tye (Cardinal) on Jul 14, 2012 at 19:03 UTC

    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        

      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.
        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        

Re^3: Page rendering bugs
by Intrepid (Deacon) on Sep 03, 2012 at 19:56 UTC

    Another CSS alternative exists (an alternative using CSS to address this horizontal-scrolling problem).

    davido offered:

    duplicate perl environments uses <pre> tags, which are a longstanding problem, not just in PerlMonks, but just about everywhere. If it's a big problem you could specify in your CSS that pre blocks should be constrained to a maximum size, and should be scrollable.

    How-dy! It ought to noted that few formatting mishaps on Perlmonks are as irritating to me (and considerable other users) as long-line posts (horiz. scrolling). The <pre> tag is indeed deprecated at Perlmonks, but is it a reasonable expectation that most users without long experience here will remember that? Plus, is it (apparently) true that users diligently check the markup they are using against the Monastery guidelines? Point taken perhaps without me going on and on about user behavior ...

    A code solution always seems attractive when one can be found. Here's one for the PRE problem on Perlmonks nodes:

    /* style frag CSS */ pre { white-space : pre-wrap }

    The pre-wrap is defined at w3.org as doing:

    This value prevents user agents from collapsing sequences of white space. Lines are broken at newlines in the source, at occurrences of "\A" in generated content, and as necessary to fill line boxes.
    and is from the CSS Level 2 spec.

    I am not on the inside wrt nuts and bolts of the Everything machine and the production of markup on PMo. So I have to leave it to someone else to work out the best way to actually implement the application of a default style setting (that is different from the default in most user agents). But a simple approach would be to just change the Common CSS for all Themes.

      best way to actually implement the application of a default style setting

      You can thank me, it was done in 2010

        If you don't want the test case ruined, then you should make the test case not risk ruinning a whole thread. That is, you should put it into READMORE tags.

        - tye        

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://981839]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (21)
As of 2014-08-27 16:32 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The best computer themed movie is:











    Results (244 votes), past polls