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

@liamquin a JS hook into XPath 1.0 would surely open many possibilities but it would still require an update to the current implementation, which is what Chrome would like to avoid.

@benjamingr there are userland libraries, but these are huge and slow compared to the current, native, XPath 1.0, which is why we're not considering adopting these, as we can use a bit of JS to crawl axes and RegExp, yet the dance is awkward and always a bit ad-hoc, but we don't have license issues, bundling issues, foreign code to watch out, etc.

Of course something that can be written in JS will be written in JS, but at the same time, we all know as soon as something is available natively, it's better for everyone, and no unnecessary bloat or slower perf are needed.

I still would like to understand if there is room for any improvement or not at all though, and in latter case I think we could close this issue as "*won't fix*" and move forward.

-- 
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-720353841