i was not aware that the html 4.x specs are so strict. I thought that chrome shows me the xpaths based on the present html file and does not create something new that is not found in the data but is then compliant with the html standards.
So my interim conclusion is, that HTML::TreeBuilder doesn't care about any specs and just analyse the underlying html code. Which is straightforward for me, someone who doesn't care about any specs :) . But i got your point. Specs are essential to have a common basis, so a html parser with the specs in mind is always preferable.Thanks for your detailed explanation and your regards to HTML::HTML5::Parser
In reply to Re^2: can't extract node with HTML::TreeBuilder::XPath
by saunderson
in thread can't extract node with HTML::TreeBuilder::XPath
by saunderson
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |