Andrea Giammarchi

@DrRataplan unless you are thinking about exposing *XPath* through `querySelector`/`All`, I am not sure how that would cover the crawling/addressing use case, but as your solution would still mean updating...

@sergeykish with XPath I can select even attribute nodes and/or text nodes, and this is gold for libraries based on template literals ... as example, this single query `//*/@*[.="${uid}"]|//*/text()[contains(.,"${uid}")]` lets...

@sirinath apparently [there's an agreement among XPath users](https://news.ycombinator.com/item?id=24940676) that v1.0 is the right version to use and eventually new features should be implemented on top of v1.0, and to be...

@rhdunn > I don't think that using Hacker News comments is good for determining that there is a consensus that XPath 1.0 is the right version to use/build on. absolutely,...

> would be great to understand better the value of proposal ~~would be great to have a conversation before a thumb down ;-)~~ but I actually agree with you the...

I'm more than open to decide any `xFilter` naming convention, as long as the feature request is clear :+1:

@answershuto > At this time, input will return true normally, but in fact there will be no input event on the div. This is quite random ... as soon as...

@answershuto what about it? ```js const div = document.createElement('div'); div.addEventListener('load', console.log, true); document.body.appendChild(div).innerHTML = ''; ``` Works pretty well to me.

FWIW, I've just refactored some code from this: ```js function notifyIfMatchesXPath(query, notify) { const flag = XPathResult.ORDERED_NODE_SNAPSHOT_TYPE; const callback = () => { const result = document.evaluate(query, document, null, flag,...

FWIW, I think Safari is right.