Not that it’ll be of any use to my regular users, but I modified Jeremy Keith’s Zoom bookmarklet to turn it into a Greasemonkey script. For more info, check out Jeremy’s article on the bookmarklet. And if you happen to be a reduced vision user that would benefit from such a thing, get Greasemonkey and install this script:
UPDATE: After thinking about it, and without asking Jeremy, I made an updated version of the script that checks to see if it found a zoom stylesheet, and if it doesn’t, applies a simplified version of Jeremy’s high-contrast zoom.css file. (This also involved lifting code from whoever wrote the DailyKos Attention script.) Give it a try:
UPDATE: (02/08/2006) Joe Clark doesn’t hate dyslexics, to my knowledge. But he’s kind of a dick to autistics. Smart guy though.
UPDATE: D’oh. This blog is quickly becoming the “continuing story of a webgeek gone to the dogs…”. The problem, believe it or not is caused by a moose. A floppy moose.
It seems that my user-Content.css file thinks that some of the MT images are ads. Clearing out the ad-blocking stuff has MT working just fine. In fact, it’s probably my fault for not just using the default directory names. I’m so dumb.
Unfortunately this just brings up another difficult choice: Ad blocking or MT? Maybe with some luck I can turn images that point to mt.cgi back on.
As a last ditch effort, I go to my daughter’s computer and fire up IE. [I know friends don't let friend use IE, but it's the only browser that works with the sites she uses (their fault, not ours).] And whaddya know? It works.
So now I’m left in a quandary: Use the browser I love, or the CMS that everyone says is so wonderful?
Right now I’m leaning to blogging in one and browsing in the other, but it makes me feel like a real sell-out. I’m hoping this is just a freak occurrence, and some sort of upgrade will make all the pain go away.