IE8, Doctype and potentially broken default behavior

2008-01-22 2 min read Ie Ie8 Microsoft Standards Eddie

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 bleeding edge, 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.

Continue reading

Another design tweak

2007-12-18 1 min read Design Firefox Ie Eddie

As you might have noticed, I’ve been a bit pre-occupied recently. And likely will be so in the future. So a design for this site has once again been placed on the back burner. I am good for a tweak-ing, however.

Looks fine in Firefox 2 for mac/pc. Opera, has a small problem, I think due to a varied em interpretation (it’s different on each platform). I tried IE6, and of course, things were missing, but the design as a whole stood up. So a few “non-lazy” changes should do the trick. Having only spent 30 minutes and using :before and :after pseudo attributes, I was surprised IE didn’t send my PC up in flames.

It just occurs to me, it would be nice if I could add a little javascript (for fun, not practical usage). Not sure what I would add it to, however. Oh well, placed on my to-do list after the real design.

Minor distractions

2007-12-05 1 min read Ie Microformats Rss Eddie

In an effort to keep my mind occupied elsewhere, here are a couple of distractions to share.

The Magical Minimalism of Microformat – The New York Times tipping their hat to Microformats

Internet Explorer 8 – Please don’t be lying, please don’t be lying, please don’t be lying…

Email Standards Project – Please turn out to be relevant

Odiogo – Convert RSS feeds to podcasts. I rarely ever listen to podcasts [ok, fine, I never listen to them], but I still like the idea.

blurry focus

2007-09-12 2 min read Ie Microsoft Eddie

I’ve been working on the same project for about 4 weeks now. 4 weeks straight. It’s the re-design of certain parts of a big site using CSS. Sounds like nothing, but the constraints of the re-design are that it must function almost exactly like the old. Therein lies the difficulty.

It is surprisingly hard to make the new act like the old. I am pretty good with my CSS, but when you have different parts that can expand to huge sizes, both horizontally and vertically, it is quite the challenge. Also, when certain expections have been set by use of tables, it is hard to design around them. There is only one widely supported html tag which can resize a collection of block-level elements similarly, and that would be a table. And yes, I have had to revert to a few tables (with some crazy CSS trickery on top).

I have found myself longing for Microsoft to catch up to other browsers, specifically regarding support of display: table* attributes, but I’m not really sure why I even looked.

Aside from the technical difficulties, my main problem as of late has been focus. I have focused so long and intensely on this one project, it is beginning to blur together. Today I was making mistakes in my code that I would have never normally made. And I had to think…for a rather long time about a conceptual problem concerning whether a certain piece of code should be put in an include, or in the calling source.

I guess I don’t really know how “long” is “long” to be working on a project. Something I will have to figure out gradually, I assume. I am glad to be able to recognize the problem, as I can now see if I can work on de-bluring my vision of the project. Maybe it simply requires a different perspective. That being said, one approach that I will take before anything else is to get a good long night’s sleep tonight.

Older posts Newer posts