Apple Releases Safari 3.1

The small cross button to close a tab often takes multiple clicks or requires me to move off of it and back on before it will register. The only thing I can think of is that I'm using SteerMouse :confused:

Been having this aswell, good to know i am not the only one, no other software etc installed, using a G7, and works fins in FF
 
Webkit still faster judging from sun spider benchmark.

Josh
It would be.

This Safari release is using WebKit code that is almost 60 days behind the current build. Obviously, Apple chose a "tried and tested" build rather than the latest and greatest, which is understandable.

The latest webkit apparently does 92/100 (or 92%) on the Acid2 test, which is almost a perfect 100 by any stretch.
 
Get used to it because every character you see on OS X will have the same applied to it. It bothered me in the past, but i have grown to like it.

It's actually not that noticable on OS X as it is on Windows.

It's down to the Windows ClearType algorthim messing up the true display of the fonts, whereas OS X renders them more accurately, however, using Safari on Windows just makes it more apparent as it's probably the only Windows app that does it like that.

Oh well, as you say, you'll get used to it.
 
It's actually not that noticable on OS X as it is on Windows.

It's down to the Windows ClearType algorthim messing up the true display of the fonts, whereas OS X renders them more accurately, however, using Safari on Windows just makes it more apparent as it's probably the only Windows app that does it like that.

Oh well, as you say, you'll get used to it.

Aye that makes sense to me. Not bothering me enough to put me off a mac by any stretch...

Thanks guys
 
It's actually not that noticable on OS X as it is on Windows.

It's down to the Windows ClearType algorthim messing up the true display of the fonts, whereas OS X renders them more accurately, however, using Safari on Windows just makes it more apparent as it's probably the only Windows app that does it like that.

Oh well, as you say, you'll get used to it.
It's not messing anything up, it just that OS X and Windows font rendering have different aims.
 
Ok, "messing up" was not the right term.

"A less accurate representation of the font compared to the render from OS X"
 
OS X renders on-screen how it will look when printed, Windows renders them best for on-screen viewing.

I'm not a DTP person so I prefer the way Windows does things, it's easier to tell if something's bold or not especially at smaller font sizes.
 
Aye, that's the explanation (which had gone MIA in my head).

I prefer the way OS X does things because I write a lot of reports, and need them to be as accurate as possible when printed.
 
Back
Top Bottom