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.
boingboing lite (Score:1)
The eye of the beholder (Score:1)
You have a problem with black text on a white background?
Bill
# I had a sig when sigs were cool
use Sig;
Re:The eye of the beholder (Score:2)
Re:The eye of the beholder (Score:1)
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;
greasemonkey? (Score:1)
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.
Re:greasemonkey? (Score:2)
Re:greasemonkey? (Score:2)
Re:greasemonkey? (Score: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;
Re:greasemonkey? (Score:1)
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.
Re:greasemonkey? (Score:2)
For some reason I thought adding stylesheets at "runtime" like this wouldn't work, but obviously it works just fine.
You're a superstar!