Re: [whatwg/dom] Proposal - Update XPath to (at least) v2.0 (#903)

@liamquin thanks a lot for the clarification, and *yes*, that makes sense. However, if XPath 3 is more problematic than 2, in terms of possible footgun within the parsing and features, I think having v2 available in JS would already be a *killer feature* compared to 1, and since nobody wants new footguns in JS, upgrading to the least problematic version that provides `matches` and `replace` (which is also in v2 IIRC), would enable a whole new world of possibilities that fit into a well known selector, instead of spanning in some CSS selector, plus JS checks, plus anything else that might result in more errors than features, for the platform.

-- 
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/903#issuecomment-707964892