Incorrectly parsed Html about anglesharp HOT 8 CLOSED

Thanks for the report - I will investigate this issue.

from anglesharp.

Hm I cannot reproduce this issue. Can you confirm that the following selector gets the element which causes the possible problems: document.QuerySelector("img.img-responsive")?

I pretty much compared AngleSharp's result with the current results delivered by the Blink engine (Opera 28) and both are the same. Am I missing something?

from anglesharp.

Yes, that's the one. It has an attribute named documentary." that includes the period, backslash and quote. I'm using the nuget assembly, version 0.7.0.37131. Is that too old?

from anglesharp.

I updated the assembly and verified that the same problem occurs with 0.8.1 as well.
Incidentally, I'm reading the file with
var html = File.ReadAllText(filename).
And parsing with an empty Configuration object.

Also: Windows 8.1, .net 4.5.

from anglesharp.

It's supposed to be like that. So this is not an issue, but rather one of HTML's "features". Please compare to the implementations in all HTML5 conforming browsers.

from anglesharp.

Just so I understand, could you explain this a bit more please?

from anglesharp.

Well, what else is there to say. I could write about tokenization in HTML5 documents, but all you need to know is that the given snippet that is responsible for the image element generation contains a dot and a backslash, which are legal characters in an attribute name. Also quotation marks are allowed. However, quotation marks (among some other characters) are parse errors.

These errors will never result in an exception or anything bad, but are indications that the page might not result in the desired tree.

HTML5 contains a lot of "features" that are included to be as backward compatible (not only with HTML, but also with former HTML error correction which was freely implemented by browser vendors, as there was no official error correction) as possible.

from anglesharp.

Understood. Some of my code converts the parsed Html into Xml (i.e. x-html) so I guess I'll have to eliminate tags that are unrecognized.

Great job on compatibility with the standard HTML5 parsing algorithm.

from anglesharp.