4714 2005-08-28 11:16:32 -0700 NodeIterator does not handle exceptions from the filter function (affects Acid3) 2019-02-06 09:03:11 -0800 1 1 1 Unclassified WebKit DOM 420+ Mac OS X 10.4 RESOLVED FIXED P2 Normal --- 17064 1 darin darin cdumez eric ian oldest_to_newest 17811 0 darin 2005-08-28 11:16:32 -0700 Looking at the NodeIterator code, it's clear that it doesn't do the right thing in the presence of exceptions. If the filter function raises an exception, the standard says that the exception should be propagated to the caller of nextNode or previousNode. But our NodeIterator implementation does not attempt to do that. Also, it calls the filter function from the "node removed" hook; it's not at all clear if it's appropriate to do so, nor what happens if the filter function raises an exception in that case. 66575 1 darin 2008-01-08 13:02:43 -0800 *** Bug 16744 has been marked as a duplicate of this bug. *** 66577 2 darin 2008-01-08 13:04:08 -0800 *** Bug 16743 has been marked as a duplicate of this bug. *** 66578 3 darin 2008-01-08 13:04:35 -0800 Need to make sure when fixing this that we pass both test cases from Acid3, the one in bug 16743 and the one in bug 16744. 66635 4 darin 2008-01-08 22:52:21 -0800 Bug 3492 now has a patch that addresses this. 69759 5 darin 2008-02-08 02:36:07 -0800 Committed revision 30089. 1502921 6 lforschler 2019-02-06 09:03:11 -0800 Mass moving XML DOM bugs to the "DOM" Component.