June 28, 2007 18:33 by
dgood
So, last night I mentioned I chose
Subtext over
dasBlog due to some rendering issues in Safari. Ok, I didn't mention it quite like that but you get the idea. Since my main machine at home is an iMac, Safari support wasn't crucial but it was the equivalent of a coin toss for me.
Scott Hanselman pointed out in his comment, rightly so, that it looked fine to him. I know what I saw, so I quickly downloaded Safari beta 3 on my windows dev machine at work to get a screen shot of what I was talking about. Unfortunately, he's right. It looks exactly the same as it does in IE 7, and as it is intended I presume.
This can't be right. I know what I saw.
At that point I was convinced that it must be an issue exclusive to OS X. I rushed home this evening and started opening browsers.
Here's what I found:
 |
 |
 |
| IE 7 on Win XP |
Safari 3 Beta WinXP |
Safari 2 OS X |
So I'm not crazy, nor is Scott Hanselman. We're both right.
On that note, I decided to get the Safari 3 beta for OS X and see if it's Safari 2 or just Safari on OS X that's the issue.
Here's Safari 3 Beta on OS X Tiger:

Safari 3 Beta OS X
So, it's obviously Safari 2 that has rendering issues. I guess the question remains how important is it to support Safari 2 on OS X? Probably not very, but it did swing my vote.
(As a side note, all this screen grabbing must have tore my monitor - I just found a dead pixel. Not happy about that.)
Cheers.
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5