Andrea Giammarchi

@annevk that proposal has gazillion comments, and I actually stopped understanding it at the second `let textToken = changes.firstChild(token);` line, as it's not clear where that `token` comes from, but...

@annevk the measurable performance here is not so trivial, but at the same time not having this in core means every site needs to take into account extra JS to...

@annevk so this is a very basic test case you can test right away in your machine too: ```html Custom Elements Callbacks Cost custom-element { display: block; } class NoCBElement...

DOM diffing is what everyone uses these days to make anything on the Web, because it's behind every single library, utility, framework, out there, because lists, baskets after buying, calendars,...

@annevk thanks for pointing me out #67 ... I think I've searched in the HTML repo and not here, otherwise bumping the XPath version *might* be part of #67 too,...

I'm *really* after having `matches(RegExp, flag)` which is currently the biggest missing feature in XPath 1.0, available since XPath 2.0 ... however, if we focused on a *new* XPath API,...

> or at least replace them with something that generates less security bugs if replaced, since work would need to be done regardless, what are the security implications of having...

Also worth mentioning that usage increased in the last years so that removing it looks indeed like a breaking change ... we just started using *XPath* extremely successfully in *many*...

@domenic I am not sure that "*folks*" included me (but I guess so ...) > I can tell this is not going to be a productive conversation, as folks intent...

@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...