Eddie Welker.com

I woke up this morning and read the A List Apart articles (that I defered reading until this a.m.).  The powers that be have decided that IE will now use a metatag to decide what rendering type (ie6, ie7, ie9, etc.) to use.  This allows for backwards compatibility.  Supposedly.

First, I don’t really care about the meta.  It’s fine… it is just one more trick to add to the pile. Generally, I agree with Eric Meyer’s points, that it’s better than browser switching.  And it is.  It’s also better than conditional CSS comments.

There are a few problems that I see, however. The first one was actually thrown into my lap as a twitter discussion between Jeremy Keith (down-to-earth web guy) and Chris Wilson (works on IE). Following the twitter-timeline, first, second, third. Apparently the default behavior for rendering a document with a HTML 4.01 doctype will be IE7. That’s right, it doesn’t fall through, it will be stuck on IE7. That is just wrong. Hopefully, both Jeremy and Chris and the other powers that be work that detail out further before Microsoft proceeds.

My second worry is the case of “edge.” Edge, as far as I am concerned, stands for <i>bleeding edge</i>, and that implies an experimental version, where results will be unpredictable.  (I infer that definition based on every other software release that I’ve heard of.) Hopefully that’s not the case, but there sure as heck better be a concrete definition of what they consider “edge”.  Hopefully they’ll throw a “current major version” in there as well.  Who knows.

The third, and probably largest concern that I have, is that we are now relying on Microsoft to include past browser rendering attributes into current browsers. So IE8 should be able to render all of IE7’s quirks, as well as IE6’s quirks. Based on the fact that Microsoft had a hard time fully flushing out all of the CSS standards for so long, whats to say that that they’ll accomplish this in full. Additionally, there are the worries that including past rendering attribues will yeild the “bloatware” that Eric mentioned.

And finally (at least for today) there’s the mess of doctype and meta.  Now you get to define things in both places.  It’s just sortof kludgy.  One more thing that I have to memorize, and I hate memorizing things.

Anyway, it’s Day one of this stuff, and there will be much discussion to come, and I’m guessing a lot of other stuff as well.