March 4, 2008
ACID3 and Konqueror
Well, the ACID3 test is out, and it’s time to see the state of the current browsers on ‘the market’
Follows a list of browsers and their results taken from http://web-graphics.com/2008/03/03/the-acid3-test/, with one addition - Konqueror was not tested there.
Edit: Added a couple more tests - thanks for all who contributed
| WebKit (Nightly - rev. 30790) | 90 < Edit |
| Firefox 3 (Nightly) | 67 < Edit |
| Opera 9.50 | 65 |
| Konqueror 4 | 63 |
| Firefox 3b3 | 59 |
| Firefox 2 | 50 |
| Konqueror 3.5.8 | ~50 (see the comments below for details) < Edit |
| Opera 9.26 | 46 |
| Safari 3.0.4 | 39 |
| IE 8b1 | 17 < Edit (thanks to all who tested) |
| IE 7 | 6-12 depending on installed plugins |
As you can see, amongst stable versions (in bold), Konqueror beats them all. Hip, hip, hooray for Konqueror (KHTML) devs! And one hip and hooray for WebKit!
This is so sad. You’re just taking advantage of a different release cycle. Besides nobody uses Konqueror 4.
Is it so hard to collaborate with WebKit?
Comment by Flavio — March 4, 2008 @ 10:29 am
Hi,
Konqueror 3.5.8 from KDE 3.5.8 with QT 3.3.8b gives 50 (tested right now).
Regards,
OdyX
Comment by OdyX — March 4, 2008 @ 10:29 am
My Konqueror (3.5.8, Qt 3.3.8b) just says “Fail” without a score. Oh, and it informs me that the page contains coding errors.
Comment by Caesar Tjalbo — March 4, 2008 @ 10:48 am
Excuses, if I copy what’s behind the picture of a dog, it says 41/100.
Comment by Caesar Tjalbo — March 4, 2008 @ 10:50 am
Even so, the only browser /in development/ that has higher score is Opera. So, why so sad? It is still a good score - 2 points behind.
Current WebKit nightly will (most probably) not appear in the next version of Safari (or any browser for that matter)
As far as the WebKit is concerned, it is being included with Qt 4.4 so we will see what comes out of it.
And P.S. I do use Konqueror 4.
@Others
My old Konqueror just crashes
Comment by admin — March 4, 2008 @ 11:02 am
Firefox 3b4pre (Nightly) scores 67.
Comment by Paul Dann — March 4, 2008 @ 11:08 am
Latest Firefox 3 nightly gets 67
Comment by Michael — March 4, 2008 @ 11:21 am
konqueror 3.5.8 from kubuntu gutsy just crashes on my machine…
Comment by knusperfrosch — March 4, 2008 @ 11:44 am
Strange. I’m using Konqueror 4.0.1 from Debian experimental and get only 49 out of 100.
This is the output.
Failed 51 tests.
Test 1: Null value
Test 2: Null value
Test 3: Null value
Test 4: expected: undefined, got: [object HTMLFormElement] - expectation 20 failed
Test 6: Null value
Test 9: Null value
Test 10: expected: result, got: - toString() didn’t work for attribute node
Test 11: Null value
Test 12: Null value
Test 13: Null value
Test 14: no support
Test 15: no support
Test 18: expected: 10, got: 1 - DOCTYPE nodeType wrong
Test 26: e1 - parent element doesn’t exist after looping
Test 27: e1 - parent element doesn’t exist after waiting
Test 29: expected: 2, got: 1 - cloned table had wrong number of children
Test 31: capture handler called incorrectly
Test 33: Null value
Test 34: Null value
Test 35: Null value
Test 36: Null value
Test 37: Null value
Test 38: Null value
Test 39: Null value
Test 40: Null value
Test 41: Null value
Test 42: Null value
Test 43: Null value
Test 44: Null value
Test 46: Null value
Test 47: Null value
Test 48: Null value
Test 51: expected: 6, got: 5 - wrong number of rows
Test 53: expected: 1, got: 0 - form’s elements array has wrong size
Test 55: Undefined value
Test 62: buckets: element has class property
Test 69: timeout — could be a networking issue
Test 69 took 500 attempts.
Test 71: missing document for test
Test 72: missing document for test
Test 73: Null value
Test 74: contentDocument failed for referencing an svg document.
Test 75: contentDocument failed on for svg document.
Test 76: contentDocument failed on for svg document.
Test 77: contentDocument failed on for svg document.
Test 78: contentDocument failed on for svg document.
Test 79: Null value
Test 80: Script in XHTML didn’t execute
Test 89: orphaned bracket not considered parse error in regular expression literal
Test 90: /(\3)(\1)(a)/ failed to match ‘cat’
Test 97: expected: one, got: fail - data: failed as escaped
Comment by oscar — March 4, 2008 @ 12:32 pm
All browsers did not pass the test. Since the acid tests are rather “academical” than real life examples, this should give developers a hint where possible problems are, and are by no means an criterium which browser is the “best” if there could be anything like that.
Standard compliance *is* important, but 10 points more or less isn’t something to celebrate, nor is this the result. Actually the result is: All the browsers show “flaws in the implementation of mature Web standards”. Thats what acid3 was designed for.
Comment by furanku — March 4, 2008 @ 12:47 pm
I saw there was an update of Konqueror to v3.5.9 (I’m using sidux, amd64 packages). Score is 51/100.
Comment by Caesar Tjalbo — March 4, 2008 @ 12:49 pm
You are right, of course. It is not the test ‘what is the best browser’, but it is not that insignificant neither.
Comment by admin — March 4, 2008 @ 2:20 pm
My Konqueror 3.5.8 from Kubuntu just crashes.
Comment by Edgeman — March 4, 2008 @ 2:51 pm
For me too, Konqueror 4.0.1 had 49. The linked page also sais 49 for 4.0.1 and 63 only for the latest Konqueror build. Konqueror 3.5.7 crashes for me. (All on openSUSE.)
Comment by Grósz Dániel — March 4, 2008 @ 4:33 pm
Weird results - since I don’t have the nightly Konq… maybe it’s a build thing…
Comment by admin — March 4, 2008 @ 4:39 pm
What about rendering bugs? In order to pass
1. The animation has to be smooth
2. The score has to end on 100/100
3. The final page has to look exactly, pixel for pixel, like the reference rendering.
The big obstacle for most vendors seems to @font-face for point #3.
BTW, please help improve the article on Wikipedia: http://en.wikipedia.org/wiki/Acid3
Comment by Lars Gunther — March 4, 2008 @ 10:34 pm
You should give also the revision of WebKit nightly. The newest one, rev. 30790, now scores 90 (!)…
Comment by Francesco — March 5, 2008 @ 8:53 am
[…] ACID3 and Konqueror […]
Pingback by Boycott Novell » Links 05/03/2008: More Low-cost Linux Laptops, One from H-P Also; Yahoo-Microsoft Falling? — March 5, 2008 @ 5:33 pm
Internet Explorer 8 Beta (8.0.6001.17184) scored a 17
Comment by Michaël Hompus — March 5, 2008 @ 10:10 pm
The only thing Iレアllycholyわたし
SCIM works in Firefox 3!! YES!!!
/anyway/, uh.. the only thing i care about with acid3 is webkit vs. gecko… they’re the only two renderers i consider viable. And once webkit catches up to gecko, life will be better. Until then, competition is great, standards are great, everybody rock on.
Comment by ethana2 — March 6, 2008 @ 2:20 am
Ok just downloaded and tested IE8 Beta 1 against ACID 3
17/100 crap everywhere…
Failed 83 of 100 tests.
Test 0: ‘document.defaultView’ is null or not an object
Test 1: Object doesn’t support this property or method
Test 2: Object doesn’t support this property or method
Test 3: Object doesn’t support this property or method
Test 4: Object doesn’t support this property or method
Test 5: Object doesn’t support this property or method
Test 6: Object doesn’t support this property or method
Test 7: Object doesn’t support this property or method
Test 8: Object doesn’t support this property or method
Test 9: Object doesn’t support this property or method
Test 10: Object doesn’t support this property or method
Test 11: Object doesn’t support this property or method
Test 12: Object doesn’t support this property or method
Test 13: Object doesn’t support this property or method
Test 15: privilege escalation security bug: text file ran script
Test 16: Unexpected call to method or property access.
Test 17: hasAttribute failure for ‘method’ on form
Test 18: expected: 10, got: 8 - DOCTYPE nodeType wrong
Test 19: expected: 11, got: undefined - document DOCUMENT_FRAGMENT_NODE constant missing or wrong
Test 20: null in getElementById() probably terminated string
Test 21: Object doesn’t support this property or method
Test 22: no exception for createElement(”)
Test 23: expected: 5, got: undefined - wrong exception for createElementNS(’null’, ”)
Test 24: expected: update() /* this attribute’s value is tested in one of the tests */ , got: - onload value wrong
Test 25: exceptions don’t have all the constants
Test 26: Object doesn’t support this property or method
Test 27: ‘kungFuDeathGrip.0′ is null or not an object
Test 29: Unexpected call to method or property access.
Test 30: Object doesn’t support this property or method
Test 31: Object doesn’t support this property or method
Test 32: Object doesn’t support this property or method
Test 33: Unexpected call to method or property access.
Test 34: Unexpected call to method or property access.
Test 35: Unexpected call to method or property access.
Test 36: Unexpected call to method or property access.
Test 37: Unexpected call to method or property access.
Test 38: Unexpected call to method or property access.
Test 39: Unexpected call to method or property access.
Test 40: Unexpected call to method or property access.
Test 41: Unexpected call to method or property access.
Test 42: Unexpected call to method or property access.
Test 43: Unexpected call to method or property access.
Test 44: Unexpected call to method or property access.
Test 45: expected: right, got: undefined - body doesn’t have floatation
Test 46: Unexpected call to method or property access.
Test 47: Unexpected call to method or property access.
Test 49: Unexpected call to method or property access.
Test 50: Unexpected call to method or property access.
Test 51: Unexpected call to method or property access.
Test 52: form.elements === form
Test 53: expected: first, got: - name attribute wrong
Test 54: expected: HIDDEN, got: hidden - input control’s type content attribute was wrong
Test 55: Invalid argument.
Test 57: Type mismatch.
Test 58: defaultSelected didn’t take
Test 59: expected: submit, got: - doesn’t have type=submit back
Test 60: attribute not specified after removal
Test 64: expected: 1, got: 0 - object is missing its only child
Test 67: when calling removeNamedItemNS in a non existent attribute: wrong exception raised
Test 69: timeout — could be a networking issue
Test 69 took 500 attempts.
Test 70: UTF-8 encoded XML document with invalid character did not have a well-formedness error
Test 71: expected: HTML, got: undefined - name wrong (first test)
Test 72: ’styleSheets.0.ownerNode.firstChild’ is null or not an object
Test 73: Object doesn’t support this action
Test 74: getSVGDocument missing on element.
Test 75: Object doesn’t support this property or method
Test 76: Failed to find element in svg document.
Test 77: Object doesn’t support this property or method
Test 78: Object doesn’t support this property or method
Test 79: ‘null’ is null or not an object
Test 80: Script in XHTML didn’t execute
Test 81: expected: 1, got: 2 - [,] doesn’t have length 1
Test 83: expected: 6, got: undefined - array.unshift() returned the wrong value
Test 84: expected: 0.0001, got: 0.0000 - toFixed(4) wrong for 0.00006
Test 85: expected: cat, got: sca - substr() wrong with negative numbers
Test 86: Argument not optional
Test 89: orphaned bracket not considered parse error in regular expression literal
Test 90: /(\3)(\1)(a)/ failed to match ‘cat’
Test 93: expected: 1, got: 2 - semantics of FunctionExpression: function Identifier … not followed
Test 94: expected: pass, got: failing - outer scope poisoned by exception catch{} block
Test 97: expected: one, got: fail - data: failed as escaped
Test 98: Object doesn’t support this property or method
Test 99: expected: www.example.com, got: http://hixie.ch/ - sanity did not prevail
Elapsed time: 9.81s
Comment by Splinter — March 6, 2008 @ 3:28 am
I’ve got 50/100 with Epiphany 2.20.3 (based on Xulrunner 1.8.1.12). Rendering is absolutely insane.
Comment by Dmitrij D. Czarkoff — March 6, 2008 @ 12:01 pm
Thanks
@Dmitrij D. Czarkoff
I’ll not add Epiphany in the list above since it has the same engine as FireFox (Gecko)… along with Seamonkey… but thanks anyway
Comment by admin — March 6, 2008 @ 12:13 pm
Well, I believe XULrunner to be worth adding as having different release cycle, and though showing more stable GECKO branch possibilities. But the only Epiphany test hardly can be a reliable source of information.
Comment by Dmitrij D. Czarkoff — March 6, 2008 @ 12:44 pm
The scores depends on your system’s speed
i repeat
THE SCORES DEPEND ON YOUR SYSTEM SPEED
re-run the test on different computers, always a different result by a few points.
Comment by non — March 6, 2008 @ 2:13 pm
Konqueror 3.5.8 crashes on kubuntu gutsy for me too.
Comment by me — March 6, 2008 @ 8:03 pm
Latest Firefox nightlies get 70.
Comment by guru — March 15, 2008 @ 4:16 pm
Latest opera gets 76 or 77
Comment by raf — March 18, 2008 @ 9:43 pm