It is odd. And so is the complete thread-jacking by someone who's posted over 32k times. Don't most people who've been around that long refuse to answer unrelated questions once a topic has been established? Seems to be pretty common practice among frequenters of forums. Even if the offending poster keeps at it, you don't have to keep answering in the thread.
Seriously, if you don't have anything to contribute to the topic at hand and instead complain (repeatedly) about conflicting information stated in someone's profile, why waste your time, and the time of the person(s) in duress? (like me) They may get email notifications when somebody responds to the thread. "SWEET, maybe somebody has an answer for me.... oh no wait, it's just that guy complaining about my profile signature information." To respond only with "..they do on my machine, so something's amiss on yours" is obvious and pretty ineffective. Especially when you do it twice.
32k+ posts in 5 years. That's nearly 18 per day. If you sleep 8 hours a night that's more than one for every hour you're awake.
~~~ In an attempt to get this back on track ~~~
I have this problem too.
I'm running 10.6.4 and Safari 5.0.2 - according to apple both up to date as of this writing. I've also got QT Pro 7.6.6 installed, don't know if others having this issue also have QT Pro installed. I also experience this exact problem on my workstation, a 2009 8-core MacPro, with the same versions of OSX, Safari, and QTPro. My wife's 13" MacPro has the same OSX and Safari versions, but no QT Pro, and she can view QT movies in Safari just fine on her machine. I refuse to get rid of QT Pro, and I don't really see why this would be the problem, but it's the only difference that occurs to me off the top of my head. I can't pinpoint a specific time this started, but if I had to guess it was after upgrading to Safari 5.
Here's Hoping that this at least let's the original poster know that other people are indeed suffering from this, so that others might be able to chime in to further discuss and hopefully find a solution. I've sent feedback to Apple about this, and I'm going to run down to the local Apple shop to see if they have any ideas. I'll post again if I find anything further.