WPT
wpt / domxpath / result-iterateNext.html
Spec: https://www.w3.org/TR/DOM-Level-3-XPath/ ↗
Runs: Chrome 155.0.8039.0 (wpt@752608e1a, 2026-09-03) | Firefox 157.0a1 (wpt@752608e1a, 2026-09-03) | Safari 251 preview (wpt@5ce815a83, 2026-08-27) | Ladybird 1.0-a9df8 (wpt@9b4cabf6d, 2026-09-03) | Servo Servo 0.6 (wpt@7e3d005d7, 2026-09-03) | Blitz a50cb8971 (wpt@a95401e4e, 2026-09-03)
View on the Blitz WPT dashboard | Open test on wpt.live | wpt.fyi
| Chrome | Firefox | Safari | Ladybird | Servo | Blitz | |
|---|---|---|---|---|---|---|
| Total | 7/7 | 7/7 | 7/7 | 3/7 | 7/7 | NOT RUN |
| Subtest | Chrome | Firefox | Safari | Ladybird | Servo | Blitz |
|---|---|---|---|---|---|---|
| Using an ordered iterator without modifying the dom should yield the expected elements in correct order without errors. | PASS | PASS | PASS | PASS | PASS | — |
| Using an unordered iterator without modifying the dom should yield the correct number of elements without errors. | PASS | PASS | PASS | PASS | PASS | — |
| invalidIteratorState should be false for non-iterable results. | PASS | PASS | PASS | PASS | PASS | — |
| Calling iterateNext on a non-iterable XPathResult should throw a TypeError. | PASS | PASS | PASS | FAIL | PASS | — |
| Calling iterateNext on a non-iterable XPathResult after modifying the DOM should throw a TypeError. | PASS | PASS | PASS | FAIL | PASS | — |
| Calling iterateNext after having modified the DOM should throw an exception. | PASS | PASS | PASS | FAIL | PASS | — |
| Calling iterateNext after having modified the DOM should throw an exception even if the iterator is exhausted. | PASS | PASS | PASS | FAIL | PASS | — |