Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

Re: Those 'wide load' posts

by grinder (Bishop)
on Oct 15, 2007 at 18:44 UTC ( [id://645002]=note: print w/replies, xml ) Need Help??


in reply to Those 'wide load' posts

It wouldn't matter if you put it in a 24 point red blinking typeface marquee and played a wave file. People would still ignore it.

The problem is more with how your browser renders the results, rather than any sin on the part of a naive user. I believe the following CSS will fix the problem:

.code { overflow: auto; } .pre { overflow: auto; }

(update: not quite correct (IANACSSM), see the solution below) And then you'll never have a wide screen again.

• another intruder with the mooring in the heart of the Perl

Replies are listed 'Best First'.
Re^2: Those 'wide load' posts (code)
by tye (Sage) on Oct 15, 2007 at 21:21 UTC
    .code { overflow: auto; }

    PerlMonks emits no <code> tags so I think that that bit of CSS does nothing here.

    I hope someone can do the footwork to validate the other half so we can just add it to the PerlMonks standard CSS, if it works well enough.

    - tye        

      "I hope someone can do the footwork to validate the other half.."
      hmm, unless I'm doing something wrong, I'd have to say that it doesn't seem to work. I've added .pre { overflow: auto; } to my Onsite CSS Markup under Display Settings, and then added some extra-wide text contained in <pre> tags to my pad - but it doesn't autowrap.

        .pre { overflow: auto; }

        Note that this sets style for the class "pre", not the element.

        You probably want pre { overflow: auto; }. Dunno what browsers support it though.

        print "Just another Perl ${\(trickster and hacker)},"
        The Sidhekin proves Sidhe did it!

      That's working on blocks with a class of 'code', and it seems the code tags get output as pre blocks with that class.

        Yes, there were either two errors in the original (thinking that <code> tags get output and that ".X" selects <X> tags) or just one typo (writing ".pre" instead of "pre"). Since the node was about <pre> tags, I just assumed the former and didn't go look up CSS selector syntax.

        To collapse the overlapping corrections from multiple replies, you'd want selectors of ".code" (class="code") and "pre" (<pre>) to get both types of blocks.

        and it seems the code tags get output as pre blocks with that class

        Sure, it seems that way to you. :) But PerlMonks <code> blocks are not output as <pre> blocks for me (because I mostly browse PerlMonks with a browser that has supported the standard soft hyphen (&shy;) for years, unlike FireFox, and so I can use "auto code wrap"). So it is better to use ".code" for selecting code blocks than "pre" (especially since the next major release of FireFox will finally support &shy; properly and "auto code wrap" rocks compared to fixed-width code wrapping so many will likely enable it.

        - tye        

Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (1)
As of 2024-04-24 13:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found