Re: [whatwg/dom] Consider specifying document.evaluate and document.createNSResolver (#67)

> [XPathEvaluator.prototype.evaluate](https://www.chromestatus.com/metrics/feature/timeline/popularity/297) has ~0.7% usage and isn't going anywhere. [XPathEvaluator.prototype.createNSResolver](https://www.chromestatus.com/metrics/feature/timeline/popularity/296) has ~0.04% and so is also likely here to stay. However [XPathEvaluator.prototype.createExpression](https://www.chromestatus.com/metrics/feature/timeline/popularity/295) is at 0.001% and could probably be left out. Which is great because that means we can very likely kill XPathExpression.

More modern numbers seem to be ~2.3%, ~0.3%, ~0.1%, all vastly higher than four years ago. (Interestingly, `createExpression` seems to have gone up from ~0.01% to ~0.1% over the past few months very suddenly; some major site now using it?)

That said, to try and write up some to-do list:

- [ ] Try and get consensus on what the WebIDL should look like (WebKit has `contextNode` optional, defaulting to `document`; Blink changed this to match Gecko a while back because the `contextNode` default was totally non-obvious and undocumented)
- [ ] Define the DOM -> XPath data model (note this includes several intentional violations of the XPath data model, as the wiki page notes)
- [ ] Define what each WebIDL operation/attribute does
- [ ] Integrate the HTML DOM special case into the DOM spec from HTML

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/67#issuecomment-496904946