found_drama

While A. committed herself to more work this evening, so did I…

I decided to follow up on this morning’s post and put forth a good faith effort at solving as many of the IE-specific issues in my CSS as I could re: Ortho…

The good news? It’s legible and more/less looking good (at least w/r/t/ the main content regions) in Internet Explorer 6¹, which is to say that the parts you (my dear reader) actually read look almost exactly like I’ve intended them². In a way, I feel like asking myself Well what did you accomplish? But that much should be easy. Ortho went from looking like a gothic kid’s worst regurgitation³ to looking like the (I hope) classy bit that I intended it to be. But there’s still a ways to go:

• ul.menu is missing border-bottom in IE6 (despite “standards compliance mode”)
• the last img in the Flickr badge sometimes drops down a full 75+ pixels despite (what appears to be) adequate clearance (width and height-wise) and proper overflow rules (and “standards compliance mode”)
• the paragraphs seem squashed together in IE (not sure yet if this is an issue with line-height or margin-bottom…)
• and of course there are the many issues with the #footer that don’t even need describing…

At any rate…  We’re a far-cry from where we were this morning.

1. At the moment, our Windows PC resources are quite limited. I’m reticent to put IE7 on the final remaining machine because I hear it (IE7) plays nice with min-width and max-height (etc.) and generally follows the rules. Well, most of the rules. And since I still have about 20% of my readership on IE (shame on y’all) and 87% of that on IE6… Alas, I need to do a little bending here.[↩]
2. It turned out to be the min-width and max-width bits of CSS. They really confuse the living shit out of the IE.[↩]
3. Black on black on black and wide as hell…[↩]

• Internet Explorer and the CSS box model

  via 456 Berea Street: very thorough explanation of IE6 deficiencies w/r/t/ the CSS box model and how to work in and around those deficiencies/limitations/quirks (…let’s start by going strict)

  (tags: CSS IE essay webdev todo)

After last weekend’s (perceived?) success getting Ortho up and running here, I was feeling pretty good.  Got it loaded into Subversion and was off and running.

Until I got my first look at it in IE6 today.  Yuck.  Even after switching to a strict doctype it is almost totally and completely illegible.  Working on that.  Fortunately, most of our readership is on Firefox (or an otherwise standards-compliant browser).  It seems there are ways around this.  It’s apparently all about not using width and padding.  Or some such thing.

We’ll see how that goes…

I think I know what I’m doing for lunch today.

Cross country road trip and I’m bringing up the rear.  Everyone else has already arrived at our destination, a Baltimore-style row house on a Barre-style hill.  It isn’t so much that I’m late but I’m the one that got stuck driving solo without a map and without any additional means to contact everyone (unless you count the change that was competitively ear-marked for tolls).  When I arrive, A., my dad, and a co-worker (MG!?) are sitting on the porch.  We had been talking about writing our very own springpunk/clockpunk anthology.  But MG has a better idea.  We’ll make up our sub-sub-genre, call it faerypunk (”…or spaghetti sauce, who cares?”) and score those publishing deals in a big way.