Make XPathResult (returned by document.evaluate(...)) iterable

[phistuck]

This will make for (let x of document.evaluate(...)) possible instead of the current pseudo old-school non-ECMAScript-compatible iterator that XPathResult currently is.

A basic and probably incomplete polyfill -
https://github.com/phistuck/monorail-enhancer-extension/blob/9e6b0b645d2df97b2e6717a35712a0d6b6229532/injector.js#L12-L29

[LJWatson]

@phistuck Sorry for this late response...

Can you provide some more information please? It isn't clear (to me at least) what you're proposing.

[phistuck]

@LJWatson - I am discussing adding the iterable declaration to the XPathResult interface -
https://heycam.github.io/webidl/#dfn-iterable-declaration

[LJWatson]

xPath is not a WebPlatform WG specification. There is an xPath wiki, but there has been no recent activity there.

Given that xPath is supported, it may be worth thinking about reviving this activity. It seems there are some Web Platform Tests already,, and you may want to write a tentative test for your proposal.

[myakura]

xPath is not a WebPlatform WG specification. There is an xPath wiki, but there has been no recent activity there.

XPath isn't. But document.evaluate() is defined in DOM3 XPath, which was a DOM WG deliverable.

[myakura]

Sadly there is no formal spec for document.evaluate; DOM3 XPath ended as a Note more than a decade ago thus it is pretty much outdated. I'm not sure if anyone is willing to work on it.
I found some notes on the WHATWG wiki but I've not seen anything xpathy in the HTML or DOM spec.

[marcoscaceres]

closing as outside scope of the wg.