Thats not how it works, its not how engine is developed, and its not how browsers incorporate standard.
It is, very much so, to an extent, how much web compliance a browser developer team chooses to implement.
Holy ****, you have really no idea ;-) ;-)
A web developer must support currently more or less only two and a half browser.
The web-standards compliant browser Firefox, Opera, Safari and then IE 8 are one.
The other one is IE 6 - and IE 7 is the half (something between the IE 6 nightmare and IE 8)
And sooner or later will be the support for IE 6 discontinued.
So, what do you want? Should Safari simulate a death browser zombie.
Okay, well lemme put this in perspective for you.
I go to a tech university, therefore know a lot of web developers. When a web developer makes a JS app, or a flash app, or a page with SQL queries, they check 3, maybe 5 browsers. Usually they're not using mac (usually in windows) so they check it with firefox first (some have been switching to chrome so they've been checking it with that first). Then they see if it works with IE. Then later,
if they both care, and have the time, they find somebody with a mac and test it with Safari. I suppose they could download it for Windows, but most of them don't, same goes for Opera.
So in the order of operations that I've seen most web developers develop pages for compliance is:
Firefox or Chrome (usually FF) >> IE (whatever version is on their Vista or XP machine) >> Safari >> Opera
Ironically, Safari 4, and Opera, the 2 browsers that score 100 on the acid3, are usually tested last. If somebody was developing for web compliance, they'd be testing their pages with Safari and Opera first, but they don't.
So while firefox may not be "right" - it's what a lot of people do their primary testing with. Few web coders I know use OS X for web dev, and even then, most of them don't use webkit, and think Safari 3 sucks, so they test in FF anyway.
So all I'm saying is that while it may not be 100% web compliance, the 70% of what firefox gets on the Acid3, is what a lot of developers program for, and then they usually follow it up with a check on IE, which gets like a 20... So all I'm saying is the acid3 may not be the best way to rate a browser at most webSITES aren't developed to succeed on browsers that pass that Acid3.
Also, I have a problem with the fact that the developer of the Acid1-2-3 test opened what he was going to test in the browser. This gave Safari and Opera something to aim towards with Webkit. Thankfully, he said he ISN'T going to tell what tests he's using for the Acid4 test, this will create a whole new breed of browsers in my opinion.
Basically, I feel Opera and Safari targetted the Acid3 test to pass it knowing what tests were on it. For a browser to be "good" by those standards, I feel it should be created, polished, finished, THEN, if they did everything right, it should be able to pass the AcidX test.
Its funny you said this is "personal preference", which I tend to agree since most people can't single out one parameter to make decision without influence of other things they care.
But forgive me for being frank, looking at those fonts, Im surprised myself that firefox does it best for people to read! I never notice this before.
Here is how it looks when I zoom it in firefox
I'm a little confused on this. Can somebody explain what the difference in text rendering is that's a
problem in firefox? The three text samples look the same for all three in the attached image, to me. I'm sure I'm missing something, but the only thing I see is that Firefox looks slightly better than the other 2 because the letters seem a bit more solid, making it a tiny bit clearer. Though I don't think the difference is enough to warrant calling the other 2 bad...I'm obviously missing something here, anybody wanna clue me in?
