There is a pending patch that fixes ACID3 test 71. However, the test still fails, even with that patch included, if you enable HTML5 parsing.
I decided to file this as a separate bug rather than just tacking it on to the existing bug 178258 on the test failure with the old parser. My reasoning is that the new parser is supposed to be doing proper parsing according to the HTML5 specification. The ACID3 test is supposed to be testing proper parsing based on the specification. So, I would think this issue is kind of independent on what the old parser might have for existing bugs.
Summary: [HTML5} ACID3 test 71 fails with HTML5 parser enabled → [HTML5] ACID3 test 71 fails with HTML5 parser enabled
The failure is: Test 71 failed: doc.open is not a function Which is interesting.
(In reply to comment #2) > The failure is: > Test 71 failed: doc.open is not a function > > Which is interesting. Never seen that. I've only seen "name wrong (first test)", but that test was changed to allow the behavior HTML 5 prescribes: assertEquals(doc.firstChild.name.toUpperCase(), "HTML", "name wrong (first test)"); // changed 2009-08-13 to add .toUpperCase() for HTML5 compat
I just verified that the current Mozilla-central trunk code passes acid3 test 71 with html5 parsing enabled. Since it always passed the testcase for bug 178258 with html5 parsing enabled, this kind of makes my entire initial complaint invalid.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a2pre) Gecko/20090813 Minefield/3.6a2pre v. Test 71 passes.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.