I broke my Wookie!
It was inevitable: my site finally broke in IE6. Funny enough it’s just the home page, but regardless it doesn’t degrade very graceful at all. Floats are going all wild and surly on me. With everything I got going on I think that I might I have to leave […]
I broke my Wookie!
It was inevitable: my site finally broke in IE6. Funny enough it’s just the home page, but regardless it doesn’t degrade very graceful at all. Floats are going all wild and surly on me. With everything I got going on I think that I might I have to leave this one to die, at least for a little while. I’m betting that most of the people that would possibly have any interest in my site wouldn’t be using Explorer in the first place, yet if they are it’s more than likely to be 7.
Obviously this isn’t the type of behavior that a standards loving, usability preaching, professional minded web designer normally exhibits, nor openly declares; but here I am. IE7 resolves no problem (for the most part) and I’ve laced every float w/ a display:inline rule to rid myself of any double-float margin bug infestations but to no avail. Holly ‘n John can’t do anything for me.
I imagine that I’ll figure it out, but truthfully the site looks so bad in 6 that I really don’t care. What the hell were they thinking when they coded that monstrosity?
Technorati Tags: IE6, web design, coding, broken wookie
No less opinionated though!
As hard as I try, there hasn’t been time to finish a post lately. Like always, I’m saving drafts of something I intend to finish, but never seem to get to. I suppose I also owe that to my distrust of my first draft! It’s either horribly written, or horribly […]
No less opinionated though!
As hard as I try, there hasn’t been time to finish a post lately. Like always, I’m saving drafts of something I intend to finish, but never seem to get to. I suppose I also owe that to my distrust of my first draft! It’s either horribly written, or horribly abrasive; I try to post the median between the two. Regardless, here’s something I experienced recently.
During my last class, I got involved in a discussion w/ some of the other students and the instructor. It started w/ one of the students remarking how they felt Firefox was difficult to work with; that it displayed things wrong compared to Internet Explorer. [Don’t sprain your eyes from the repeated, intense rolling you’re experiencing at this moment.]
I, and the instructor quickly jumped to the aid of our friend the Fox explaining that it’s the friendlier of the two, and that it actually cares about web standards. We explained that we coded in FF first, then debugged IE afterwards. They couldn’t understand this logic, as they were told by another instructor that they should be designing for the browser w/ the larger market share. [Proper stretching will prevent severe eye sprainage.]
Unfortunately I didn’t think of this at the moment, but I had to share this regardless. For the sake of the web’s future we all should be coding for Firefox and debugging IE afterwards. I’ll explain. Since we know that FF is pretty compliant w/ web standards it goes w/out saying that we are learning the correct way to code by doing so. By coding for IE, we’re learning things from a skewed perspective. So here we have another graduating group of designers who are perpetuating IE and all the issues inherent to it, forcing those of us learning standards based markup to continue utilizing hacks, inevitably wasting all of our time.
So essentially (at least to me) if you’re unable to get it to look right in Firefox, then your code isn’t right; or more lightly said: you’re not using best practices. I know that’s harsh, but I think it has to do a little w/ me getting tired of this school. Beyond that I won’t say anything further.
Technorati Tags: coding, web standards, Internet Explorer, Firefox, XHTML, CSS
