Safari (WebKit) passes acid3

[E6600]

Come on! These are nightly builds, every couple of days, something is fixed.

An interesting post:

johnnysaucepn Says:
March 27th, 2008 at 3:32 am

Remember, 100% is only one-third of the criteria for passing the test… The game is still afoot

[downphoenix]

Gecko > Webkit.

Apple sucks.

[E6600]

Originally Posted by downphoenix

Gecko > Webkit.

Apple sucks.

Google, Nokia, Trolltech and others use/contribute to WebKit

[neowolf]

Originally Posted by chedabob

As in, been around much longer.

Something Witty Goes Here

Oops

A year's not all that much longer. (Remember WebKit's derived from KHTML rather directly.) They just both take fairly different perspectives on how to develop their respective engines. Gecko's tended to focus primarily on the browser experience. KHTML's focused heavily on standards compliance and coding guidelines. WebKit's taken more of a hybrid approach between the two since it's inception.

[E6600]

Originally Posted by neowolf

A year's not all that much longer. (Remember WebKit's derived from KHTML rather directly.) They just both take fairly different perspectives on how to develop their respective engines. Gecko's tended to focus primarily on the browser experience. KHTML's focused heavily on standards compliance and coding guidelines. WebKit's taken more of a hybrid approach between the two since it's inception.

WebKit, now, is ahead of KHTML when it comes to standards, KHTML was the best rendering engine to start with. Right now I'm on Konqueror, Konqueror feels sluggish on the GNOME desktop, understandable, but it is a rocket when it comes to loading and rendering pages. The worst bit about Konqueror, you'll find sites that wont work with it, so sometimes I have to use Firefox. Konqueror will switch to WebKit, can't wait for that.

[NapalmRiot]

I thought I would smell tears from a thread like this...

but chedabob is right. If a browser can do it right without worry about LSD3, then what's the point?

[2pro4show]

I don't get what all the fuss is about. Would I, the average PC user, really give a shit whether Firefox passes a test or not? If it passes this test, what enhancements do I get while browsing? All just seems like some weird behind-the-curtains evaluation. I only care for what I can do and see while browsing, and Firefox is the best at that.

[E6600]

Passing the test means that the browser complies to most/all standards. If you think it is OK to have a browser that ignores web standards you are wrong. Ever came across IE-only sites? That shouldn't of happened if IE has implemented web standards.

[2pro4show]

Originally Posted by E6600

Passing the test means that the browser complies to most/all standards. If you think it is OK to have a browser that ignores web standards you are wrong. Ever came across IE-only sites? That shouldn't of happened if IE has implemented web standards.

I think "web standards" is a bunch of crap since I've never seen them interfere with anything I was doing or trying to do. Why should I care if it doesn't bother me?

[chedabob]

Originally Posted by 2pro4show

I don't get what all the fuss is about. Would I, the average PC user, really give a shit whether Firefox passes a test or not? If it passes this test, what enhancements do I get while browsing? All just seems like some weird behind-the-curtains evaluation. I only care for what I can do and see while browsing, and Firefox is the best at that.

You won't notice any difference.

Originally Posted by Mozilla

I was looking over the spreadsheet covering Mozilla’s Acid3 failures, and it struck me that very few of the fixes would substantially improve the Web or the browser. They are bugs and they will be fixed (except maybe SMIL… wtf?), but they don’t impact authors or users at all. Looks mostly like an opportunity for grandstanding about “commitment to standards.” I think testing createNodeIterator while text nodes don’t interoperate is both misguided and hypocritical. Besides, commitment to standards is strong at Mozilla, where we don’t constantly seek to rubber stamp our own implementation.

Rob Sayre’s Mozilla Blog » Blog Archive » Acid3 is basically worthless