Does anyone know why Safari on Tiger is saying goodbye to Rabenhorst? And if someone knows, can they tell Kai so he can fix it and I don't have to rewrite an article every time because I wanted to check something with him again?
The strange thing: when I turn off JavaScript with PithHelmet on his site, nothing happens. But his site has no JavaScript - only the Jabber status (which, by the way, is displayed extremely large without JavaScript activation) is embedded via an OBJECT tag instead of an img tag. Could it be the OBJECT tag for PNGs that sends Safari to the Orkus?
Ah, yes, after a bit of digging, it seems to be the case. Go to this page and you will have the same problem - Safari crashes. Apparently, the OBJECT tag is used to display PNGs on older IEs as well - the same PNG is referenced via an OBJECT tag and an included IMG tag. Unfortunately, this leads to crashes with Safari 2.0.
Why disabling JavaScript (not disabling plugins, which one would rather suspect with the OBJECT tag!) leads to Safari not crashing and the PNG being displayed incorrectly (too large), I honestly don't quite understand ...
Oh, and the bug with object tags seems to have existed for a long time - the oldest reports I found in Google are from 2003. It would be nice if Apple would actually fix the bug. Or someone else, since the source is now available.
By the way, OmniWeb - although it also relies on the WebCore framework - does not have this problem. It would have been too easy ...
Update: the culprit has been found. It was the WebDevAdditions for Safari - I simply installed the current b11 and everything works normally again.