Here is a list of all of the failures we currently have, and their associated Bugzilla bugs:
Failed 35 tests.
Test 0: expected: pre-wrap, got: normal - found unexpected computed style
Test 1: method [object NodeIterator].nextNode() didn't forward exception
Test 2: expected: [object HTMLElement], got: null - expectation 13 failed
Test 4: expected: null, got: [object HTMLIFrameElement] - expectation 21 failed
Test 6: expected: [object HTMLTitleElement], got: null - failed to handle regrafting correctly
Test 8: Null value
Test 11: when trying to surround two halves of comment: wrong exception raised; code = 3
Test 13: collapsed is wrong after deletion
Test 18: expected: 10, got: 8 - DOCTYPE nodeType wrong
Test 23: no exception for createElementNS('null', ':div')
Test 25: failed to raise exception
Test 26: e1 - parent element doesn't exist after looping
Test 27: e1 - parent element doesn't exist after waiting
Test 35: expected: 0, got: 1 - :first-child still applies to element that was previously a first child
Test 36: expected: 1, got: 0 - last child did not match :last-child
Test 37: expected: 1, got: 0 - :only-child did not match only child
Test 38: expected: 0, got: 1 - removing all children didn't make the element match :empty
Test 39: expected: 1, got: 0 - :nth-child(odd) failed with child 0
Test 40: expected: 1, got: 0 - part 2:7
Test 42: expected: 1, got: 0 - rule did not start matching after change
Test 44: expected: 0, got: 1 - misparsed selectors
Test 59: expected: submit, got: - <button> doesn't have type=submit
Test 64: expected: ./test.html, got: test.html - object elements didn't resolve URIs correctly
Test 66: expected: null, got: #text - wrong localName
Test 69: expected: 33, got: 0 - SVGSVGTextElement.getNumberOfChars() incorrect
Test 71: UTF-8 encoded XML document with invalid character did not have a well-formedness error
Test 72: expected: TITLE (first test), got: TITLE - undefined
Test 73: Undefined value
Test 74: expected: 10, got: 1 - click event handler called the wrong number of times
Test 75: getSVGDocument failed for <iframe> referencing an svg document.
Test 76: Value undefined (result of expression anim.beginElement) is not object.
Test 77: expected: 0, got: 100 - Incorrect animVal value after svg animation.
Test 78: expected: 4776, got: 5550 - getComputedTextLength failed.
Test 86: calling setMilliseconds() with no arguments didn't result in NaN
Test 92: Function object's prototype's constructor was ReadOnly
Elapsed time: 4.03s (debug build)
There are also some visual failures:
16760 - HTML Object elements should not render 404 content
16770 - Acid3 expects :visited styles to update after iframe load
17085 - Acid3 Ahem test font no longer loads properly
Bugs discovered during testing, but not required to pass Acid3:
8961 - document.write() does not flush plain text (shift-click on the A to see failure)
14256 - Inspector hits assertion while inspecting image in Acid3
17004 - Assertion clicking on n/100 in Acid3 results
This is certainly not a full list of all the bugs which will need to be fixed before Acid3 will pass 100% in WebKit-based browsers. However, this is all the bugs that I know to be visible at this time.
All Acid3 bugs have Acid3 in the title, you can find them using this query:
Your comments (and help fixing them) are certainly appreciated.
Thanks,
Eric