Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Re^3: Page rendering bugs

by Intrepid (Deacon)
on Sep 03, 2012 at 19:56 UTC ( #991508=note: print w/replies, xml ) Need Help??

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

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

I run two CSS sheets in my Perlmonks reading / posting which I do consistently using only FFx (Firefox). One was nicknamed "NYPM Blue" by me a long time ago and is set up in User Stylesheet Settings in Settings. The original 6 Themes include the Dark theme which I have toggled in User settings. So the Dark theme is CSS-cascaded previous to my custom NYPM Blue sheet. I've got the NYPM Blue sheet housed at You, the public, can look for yourselves.

In addition, I have a UserStyle (a Mozilla / FFx thing) for the Perlmonks chatterbox in the sidebar, and one for CB60 in the sidebar (just applying the stylesheet doesn't put either in the sidebar: see other nodes here on PMo for how to do that) (both living under here, to browse code –use Stylish to install them) …and as an (unpublished) work in progress, a sheet for Threaded Discussion ("multinode") pages (which might or might not be merge-able into one of the other stylsheets).

  • (1) The Chatterbox restyling is part of the NYPMBlue Style (PMoNYPMBlue.UserStyle.css) rather than being in a separate CSS sheet file. –Intrepid 2012-09-03 Eastern Daylight Time

Replies are listed 'Best First'.
Re^4: Page rendering bugs
by jdporter (Canon) on Sep 04, 2012 at 14:29 UTC

      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        

Re^4: Page rendering bugs
by Anonymous Monk on Sep 04, 2012 at 01:57 UTC

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

    You can thank me, it was done in 2010

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://991508]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (4)
As of 2017-06-24 20:07 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (562 votes). Check out past polls.