I'm happy with Safari and have no intentions to switch.
Read this one:
http://daringfireball.net/2008/04/firefox_3_safari_3
Ok, I'm reading your link. It says first and foremost that Firefox3 does not get 'lighter' when it's in the background--that it's always DARK unlike Safari and that the Firefox theming engine won't allow it to. Um... either that changed since he tried the BETA (as in it's not the final release) or he's just plain wrong. I'm using FF3 right now and if I put it in the background, it goes light just like Safari with the default theme.
I wasn't even aware there was a dictionary feature for Safari. I'll have to try that out. I wouldn't be surprised if there was an add-on to support something similar, though. I've never even considered it before. Let's see...yup right off the bat here's one:
https://addons.mozilla.org/en-US/firefox/addon/68
It goes on and on and on about the page load progress indicator being "a total win for Safari" even though the "Fission" add-on for Firefox3 gives it the same functionality. I guess the reviewer didn't really look into what Firefox is capable of doing with a little customization. What he fails to realize is that Firefox's design has always been to let extensions handle custom features. And you have to admit a dictionary while useful isn't exactly directly related to web browsing itself. Safari is set up to use MacOSX features whereas Firefox is designed to run on several platforms, not all of which look and/or act like a Mac. And yet with a few clicks you can make it look and behave almost identical to Safari if that happens to be your cup of tea.
I miss things in Safari like Middle Click over a tab to close it. Unlike Firefox where I can get a tab package add-on to solve my tab woes, I'm stuck with Safari's default behaviors and if I don't happen to like some of them, too bad. It's the Jobs way or find another browser.
Why not? They are competing browsers. They use different rendering engines and both of those have got full marks in ACID 3.
I'm not sure why you don't seem to understand the concept that Web-Kit only made certain new standards work "just enough" to pass the Acid3 test specifically. They do not support those standards enough to ACTUALLY BE USED in day-to-day practice. A Firefox developer was quoted as saying that is not the way they do business with their browser, making spotty changes just to pass a specific limited test but then have no actual support for the technologies involved. They intend to add full support for those standards and when that's finished it'll past that part of the test. In other words, Web-kit when examined looks kind of dumb to short-change their users like that. They pretend to be able to do things they cannot do. It's deception. It's why some sites won't work on Safari but DO work on Firefox. Firefox isn't half-baked in those areas.
Maybe you prefer deception over real features, but I do not.
Clearly.