3 ms·
That makes sense about xpath not being an XML dialect. Its much easier than .NextSibling.ParentNode... etc etc. I always try to go for the path of least resist
by account-5 3y ago
That makes sense about xpath not being an XML dialect. Its much easier than .NextSibling.ParentNode... etc etc.
I always try to go for the path of least resistant.
- masklinn 3y ago> That makes sense about xpath not being an XML dialect. But the point is that it follows TFA's advice: while it's a DSL for working with XML, it's not an XML language. Wish that XSLT had been the same, it could have been so much better. > Its much easier than .NextSibling.ParentNode... etc etc. I don't think that has any relation. Also it does look a lot like what you wrote: ./following-sibling::*[position()=1]/parent::* even if you use the various shortcuts, since there is none for the next sibling or following siblings: ./following-sibling::*[1]/..