NodeIterator fix leaves us with 4 points to go
WebKit was still failing on test 2 of Acid3. That’s a NodeIterator test. The problem was a simple one: While NodeIterator objects were rigged to update themselves when nodes are removed from the document, there were a couple of edge cases that weren’t handled quite right. I tried to fix this about a month ago, but got confused. This time I was able to keep my head straight and it took me less than an hour to fix the bug.
We’re passing 96/100 tests now. There are only 4 points to go to get to 100 points. There are also a few loose ends that don’t cost a point and also some reports of a few failures that some see on their computers, but don’t affect most computers.
We’re closing in on 100%!