Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TorgoX (1933)

TorgoX
  sburkeNO@SPAMcpan.org
http://search.cpan.org/~sburke/

"Il est beau comme la retractilité des serres des oiseaux rapaces [...] et surtout, comme la rencontre fortuite sur une table de dissection d'une machine à coudre et d'un parapluie !" -- Lautréamont

Journal of TorgoX (1933)

Thursday August 18, 2005
06:10 AM

BoingBoing BongBong

[ #26351 ]
Dear All,

To make BoingBoing's crappy 1997-style HTML look tolerable: install URI id, then add this to your ~/.mozilla/firefox/[jumbly stuff]/chrome/userContent.css file:

body#www-boingboing-net,
body#www-boingboing-net *
{
  /* Or however you like it: */
  background-color: black !important;
  color: white !important;
  font-size: 20px !important;
}
body#www-boingboing-net td[width="125"],
body#www-boingboing-net td[width="150"],
body#www-boingboing-net td[width="800"][height="90"]
{ display: none;  }

Then restart Firefox for the change to take.

CSS is fun.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • There's also BoingBoing Lite [dialedin.us], which lets you filter out some of the crap content along with the crap layout!
  • crappy 1997-style HTML look

    You have a problem with black text on a white background?

    --
    Bill
    # I had a sig when sigs were cool
    use Sig;
    • No, it's mostly the blindingly small font size that got me to write this. While I was at it, I just up and changed the font size, and killed the inane graphics.
      • Ah.

        Way too many websites have *fixed* widths wider than standard printer margins (e.g., Catalyst.org's Trac wiki) and fixed font sizes so the VIEW|FONT menu doesn't work. You shouldn't have to drop into CSS to fix these, if people followed usability / accessibility standards, we would just set our browser preferences to "Old Eyeballs" or "Young Eyeballs" and all would be fine ...

        Cheers!
        --
        Bill
        # I had a sig when sigs were cool
        use Sig;
  • More curiosity than anything else, but is there a specific reason for why you're using userContent.css instead of a quickie GM script ?

    It's probably my lack of familiarity with the chrome stuff and also my reluctance to mess with Firefoxy internal files speaking.

    • I'm just more at home with that CSS stuff than GreaseMonkey.
    • BTW, how would you (or you! or you!) do this as a little GreaseMonkey script?
      • Uh, I just whipped this up, so I'm not entirely sure if it's according to spec (tell me if it isn't etc). Behold, TorgoBoing 0.1

        // TorgoBoing

        // ==UserScript==
        // @name        torgoboing
        // @namespace     http://diveintogreasemonkey.org/download/
        // @description   What usercontent.css can do, Greasemonkey can do too
        // @include       http://*boingboing.net/*
        // ==/UserScript==

        function addGlobalStyle(css) {
            var head, style;
           
        • I suppose I should provide some explanation :) Oh, bother.

          Setting the sidebar divs to not display was my first choice, since that's the ugly part of the page. I also have a preference for having the page content take up the entire screen width, so I did my page widening hack. Hardcoding the pixel size is bad, I know :( Was too lazy to figure out a nicer way to do it. This is how I would have done it myself.

          I commented all of that out ultimately and replicated your usercontent.css logic though.

        • Wow, this is great! Thanks!

          For some reason I thought adding stylesheets at "runtime" like this wouldn't work, but obviously it works just fine.

          You're a superstar!