“The latest beta of the WebKit engine that runs beneath Apple’s Safari and other browsers has achieved 100/100 score in the Acid3 test, which means that the Safari 4 beta has reached a significant milestone in terms of web standards compliance. Opera closely follows Safari while Microsoft’s Internet Explorer versions score the lowest marks,” Christian Zibreg reports for TG Daily.
“The Acid3 test is generally considered as a benchmark to determine how well a web browser follows web standards and at least as of now, Safari 4 beta is the most compliant browser. To pass the test, a browser has to use default settings, the animation has to be smooth, the score has to end on 100/100, and the final page has to look exactly, pixel by pixel, like the reference rendering,” Zibreg reports.
“The WebKit team said that the perfect score is a result of the fast layout engine and optimizations relating to the Document Object Model (DOM) and JavaScript engine,” Zibreg reports.
Full article here.
WebKit is going to get beat up in the school yard for ruining the curve.
Thanks to Squirrelfish Extreme.
Way to go apple. You show them. I am very proud.
Safari, so good…
From the article: “…WebKit has raised the stakes of the game, which may prompt rivals to optimize their JavaScript and layout engines and comply with web standards. The more browsers render pages the same way, the less code tweaking is required to tailor a page for a particular browser.”…
“If JavaScript performance increases, we should see many more desktop-like web applications in the future.”
Gee… I wonder if MicroSoft wants to get as web-complianty with IE8 as it says it does? NotSafarisIcantell.
My browser is an honors student.
And the best in class browser should render porn with greater results. That’s why summa come louder.
safari rocks!!!!!!
And yet on the “What Works” test, crappy old IE6 is compatible with more Websites than any other single browser.
I’m not saying IE is good or anything like that. I’m just asking how relevant is the ACID3 test when developers still almost uniformly only test with IE.
Firefox testing is an after thought, and Safari testing is almost never done.
Ask a developer, “Did you test Opera, Camino, or make sure your design was within Acid3 parameters” and you get “Huh?”
Google McCloud, you are right – unfortunately. The reason has little to do with how compliant the browsers are with “web standards” applied by the non-proprietary industry, but with the web-design software published and sold by MS. And, of course, IIS – the web server software they provide along with the rest of their server package. They have built in a lot of “not industry standard” “features” that work only with IE (but they will license your browser, for a price) and IIS. Looks good, except when broken, but only works for IE.
All the designers I know (except for enterprise wonks) test both Safari and Firefox along with IE. It used to be Netscape, rather than Safari … things change. Also, many test Firefox and Safari on both platforms. Also a new model.
How is this news now?
I downloaded Safari 4 in July from the Apple Developer Page, and it has not been updated since.
I just revisited the Acid Test to make sure, but my browser scores a perfect 100, and if that is the case now, then it must have been doing so since the beginning of July.
Hmm…
First off, webkit is not the same as Safari beta 4. This article will only be accurate when apple puts the latest nightlies into their safari 4 beta.
The 100 that webkit scored on the Acid 3 test over the summer still did not pass some of the requirements of the test. The rendering needed to be smooth and 30 fps. That accomplishment only occurred since the inclusion of Squirrel Fish Extreme. Great job webkit team.
@John
“How is this news.”
Actually there are two parts to the Acid3 Test. First is the rendering, the second is the timing and speed. Both tests have to be passed perfectly for the Browser to claim full compliance.
While some builds of Webkit passed the rendering test last summer, it has only now passed the timing test.
@ Google McCloud : “when developers still almost uniformly only test with IE.”
This is just not true actually. 5 years ago, you might have had a point but these days with Firefox and its approximately 25% of the market, only a foolish developer doesnt look at their work in other browsers.
Most devs I know test for IE 6 and 7, FF 2 and 3, and Safari. It has to be said that most problems are still isolated to IE and MS’s seemingly inability to create a standards compliant browser. Opera, FF and Safari with their stricter adherence to standards, generally dont need a lot of attention at all. Its just good practise to test. And yes I am talking about good clean code here, not some shyte pumped out from .Net
@DLMeyer
It pisses me off to have to test our site at work in IE when I do updates. It seems everything works great in safari and firefox on both Mac and Windows but as soon as it touched IE.. I have to redirect and adjust crap so it looks ok. Maybe I should just add a redirect to installing safari or firefox
” width=”19″ height=”19″ alt=”raspberry” style=”border:0;” />
I don’t know what planet you guys are from, but at my work, tests are done using IE, Firefox, and then finally Safari. And, even though our web sites are developed using Adobe Dreamweaver, there are many pages that don’t work near as well using Safari, especially stuff like web tabs. There’s still much to be done.
I don’t think you’re right about IIS having “IE only features” built in. I develop asp.net sites and host them on IIS for a living, and while they must be hosted on a Windows server, the client can be using Windows/Mac/Linux, IE/Safari/Firefox, or whatever as long as it’s standards-complaint.
I have never encountered a built-in feature of asp.net (Visual Studio 2005) or IIS that was “IE-only”, although you definitely do need to tweak the CSS output from Visual Studio 2005 if you want it to be cross-browser instead of IE’s broken CSS. But we’re talking minor tweaks here that any web developer worth his paycheck shouldn’t have a problem implementing.
Just curious, but why is the WebKit nightly app 85+ MB ??