I’ve been hearing people virtually *whine* their ass off for the past months about Firebird 0.6 being delayed. Of cause a 0.6 milestone is good for the project, but it’s value is not really that huge.
I always use the very latest firebird nightly-builds, so I had really no care in the world about when 0.6 was going to be released. This is why I do not understand all the other l33t firebird-build users were screaming for 0.6. I can understand many wanted it released because it would send a signal to the end-users that development was still active and of cause it’s better to release a more stable version (0.5 had a few nasty crashes).
Almost every week on the Firebird Forums, people posted “When will 0.6 be here” and “build is good, but still no 0.6″… I usually posted a reply stating that 0.6 should really be nothing to them, because the day after 0.6 was released, they would still use the nightly-builds, but still they wanted their precious 0.6.
*Then finally* they got their precious, and good it is (better than 0.5)… But make no mistake that the day after it was released, all those people who were urging on 0.6 were using their latest nightly again… now, in a few weeks.. people will start asking for 0.7, and what will I tell them? The same story, will they listen? no!
Anyway, to summarize, if you didn’t already know, firebird 0.6 has been released… It kicks both Mozilla and Internet Explorer’s ass. I stopped using IE a long time ago, now I only use it when I need to see a page which knows nothing about W3C standards
Download it now (installer)
I still have a question on how IE understands the placement of my images in this blog, and Gecko doesn’t… anyone?
Update: Thanks goes to Christian for giving me a hint on how to fix the problem :)

>I still have a question on how IE
>understands the placement of my images
>in this blog, and Gecko doesn’t…
>anyone?
If you refer to that the picture in the posting “Matrix Fun” is sort of “sliced” by the previous item, then Gecko is actually right and IE wrong, according to W3C (if I understand the spec correctly).
To fix the problem, just add a “clear: both” CSS rule to the DIV with the grey border.
Fire at will, Tom :)
Thanks, needed to add “clear: both;” a few places, but it worked… :)
Thank ya :)
Great :-)
The “explanation” is that floats, including those made by align=left/right in the IMG tag, according to the spec does not affect block elements but only the text inside them.
It looks as if IE does not allow a floating element to extend below the element in which it is contained.