Closed ilushka85 closed 12 years ago
I'm in the middle of testing a new HTML parser (which is a complete HTML5 implementation) which appears to be highly compliant and working a lot better than the existing one, if it passes all the tests it will probably solve this problem. Will follow up later.
Is it the one currently checked in to github?
Yes, I also just added a new branch called "newparser" with the new parser integrated into CsQuery. There are some integration tweaks I am not done with, particularly as it relates to parsing fragments, so some tests aren't passing right now. But generally speaking it's working amazingly well - it implements the complete HTML5 ruleset, and the original java codebase is well supported.
It's not clear if the person who did the port to C# is still involved. But considering I've done only a few hours of work on integration, and ~90% of the tests are passing already, I am very optimistic about this.
Just tried new branch and my sample still fails under it.
Well that code is definitely not ready for prime time, did you just try to drop it in, or did you create a simple test case?
If it's actually running/parsing the doc and it appears to work generally (but just not finding that element) its probably something else, I can look into it later. Maybe there's a duplicate ID?
Checked for duplicate id's.... theres a lot of elements surrounding this one it doesnt find in old code base or new.
I'll take a look later.. have to do some chores while the sun it up. If you want you can add that document under CsQuery.Tests\Resources so I have it in its entirety and make a pull request. Or just email it to me.. it looks cut off/mangled here on github.
Nevermind im a retard my browser had different source to it then my htmldoc object stupid site outputs different based on browser.
Glad you figures it out!
the below html does not find the element via htmldoc["#itm_num"];