Hit “refresh” in your browser window any time you like and there’s likely to be changes to the look of the site, since I decided that tonight was the night to scrap Movable Type’s default style sheets and start afresh. At this moment I’m toying with a variety of things, most notably the page heading.
Those of you that viewed the “returning soon” page at this domain over the last few months may have noticed that the “pretty spiffy” titling of “decaffeinated” was completely text-based and CSS–controlled. Then again many of you may not have; particularly IE5/Mac users, who saw nothing at the time and are currently experiencing some pretty funky layout errors, too. Never one to begrudge a browser (ha!), I’ll surely identify those problems in good time and perform a few Windows browser tests while I’m at it. For now though, I’m still toying and testing in Camino.
In reference to my pure-text heading (a styled
<h1> element, with a similarly styled
<p> laid atop to give the impression of shadowing); I’m wondering what the semantic impact of this technique is, exactly. Probably negligible, in which case it only reflects 2 things:
- That I am relentlessly anal about semantics, particularly when it comes to the old-school-favored method of using images instead of text.
text-shadow needs to be implemented by many browsers, pronto! Else I am forced to torture myself over minutiae forever.
Disappointingly, Microsoft Internet Explorer 5.2.2 (for Mac) fails to render this site properly… and I’ve barely implemented one tenth of the CSS I was planning for the coming days. For some reason, IE takes it upon itself to utterly disregard the natural flow of the page, having the paragraphs of my entries sit right on top of my “masthead”
<div>. Even adding superfluous CSS statements to my
position: static; (which I shouldn’t need to implement) does nothing to slow the shitstorm of misrendering this page experiences under IE5/Mac.
UPDATE: IE5 feels that once the
<h1> (for which the “masthead”
<div> is a container) is taken out of the flow of the page using
position: absolute; (a necessary evil, unfortunately), that it’s open season on that
<div>. As far as IE5 is concerned, that
<div> is empty and serves no purpose, so it’s free to render right over the top of it. It feels like I’m copping out by playing IE5’s stupid little game, putting a non-breaking space in that
<div> just so it doesn’t freak out, but too many people use this trashy browser for me to disregard it altogether.
Safari (Beta 60) fares even worse; it doesn’t even load the page before it crashes. But to be fair, it is only in beta and it doesn’t actually crash… it “stops responding”. Dave Hyatt (though I can’t find the entry… which makes me wonder whether I imagined it all or not) reported other CSS-engine crashes earlier this week when some “web freaks” tried using a few CSS3 pseudo-selectors they knew worked in Mozilla… I guess I can only wait for beta-64 and beyond.
OmniWeb has no trouble with the page, Gecko browsers (Mozilla and Camino) have no trouble with the page, Opera has only a little trouble, and iCab… well let’s just say that iCab does its best, shall we? I’ll be testing Windows browsers tomorrow when my roommate gets up (my PC resides in his room nowadays, since it doesn’t get any use in here), and I can only hope that they fare better.
The most thoroughly disgusting thing about this whole mess it that the only CSS I’ve really implemented is working on the masthead of the page. What the hell is going to happen when I work on the rest?
It’s past 6AM, I’ve been coding for nine hours straight, I think I’ve hit “refresh” about a hojillion times tonight. The page is a long way from finished, but at least it’s looking decent and is reasonably useable. It’s time for little boys to go to beddy-byes. Good night.
According to Jay Zee, Cynthia goes down every 60 seconds, which is pretty impressive if you ask me. Apparently she wears clean underwear too, something that’s hard to find in a girl like Cynthia.