2008-06-26 (Non-Standards|IE) do fail again( and again)+\.

As if it was not enough that IE terrorizes the whole Webdesigner Community, ongoingly breaks the Budget and re-introduces Bugs over and over again (in short, it stinks), even experienced with these circumstances you swear not to whine about all this any longer, you can still find out about another IE-Demo of the concept “Breaking-Standards” that fails often in Information Technology (IT).

I lately ran over a project that needed to get a time-boost to save the customers ass. Well in planning we were able to create a robust workflow to come to a static version leaving no trails behind at super high-speed. But in the end it did not work in IE. Even though it worked in the dynamic development version, it came to my attention that the tools we used to create the static version were not able to handle conditional comments. Or better say: the HTML inside (conditional) comments. Well, because they were comments and the URIs inside the non-standard HTML used inside comments was not parsed by all XHTML based tools because – they were comments. That easy it is. We were able to fix it anyway with some Regex magic on the very useable Multi-File Replace in Eclipse.

Another thing to rant about is the “Firebug for the poor” microsoft released some time ago. Okay, it’s better then nothing but it is not much more then nothing. A “Tropfen auf den heissen Stein” as we say in german.

Rant mode off now.

The Madness will continue and we need to deal with it. Hopefully they will not release a new version that often so that things will not get much more complicated that fast. To be constructive, it is suggestable to offer something like a gecko-tab in IE so that Internet Explorer users can switch the rendering engine by default. And maybe there is need to ship Windows with Opera some day. You never know