Here are a couple screenshots:
When you first load the page, you get
something like this,
and you have to scroll across to read the postings, like this.
-- Burvil
Whoopsy :-)
/me edits [id://541592|the offending node]
--chargrill
$,=42;for(34,0,-3,9,-11,11,-17,7,-5){$*.=pack'c'=>$,+=$_}for(reverse split//=>$*
){$%++?$ %%2?push@C,$_,$":push@c,$_,$":(push@C,$_,$")&&push@c,$"}$C[$#C]=$/;($#C
>$#c)?($ c=\@C)&&($ C=\@c):($ c=\@c)&&($C=\@C);$%=$|;for(@$c){print$_^$$C[$%++]}
This is an on going issue that arises when people post using pre tags and long lines, or long lines without anything the browser feels it can break the line on. There is no reason at all to use pre tags and that can be fixed - consider the node.
Sometimes long URLs or similar data crop up in posts and generally can not be wrapped by the browser because there is nothing the browser feels comfortable breaking the "word" on. In most cases that problem can be worked around by putting an occasional space in the string - looks fine visually and now the line can be wrapped.
You can /msg the person who posted the objectionable material. If that doesn't do the trick and you feel strongly about it, you can always do a little down voting - doesn't fix the problem, but you may feel better afterwards. :)
DWIM is Perl's answer to Gödel