htmlparser2 adapter uses no html-encoding in text nodes

[inikulin]

htmlparser2 adapter uses no html-encoding in text nodes

[fb55]

jsdom's entity decoding isn't entirely spec compliant & should be replaced with the parser-provided alternatives. htmlparser2 has a decodeEntities option, which results in the same behavior.

[domenic]

The more of that kind of thing we can move into the parser, the better. I am not exactly sure how to do that, but we'll look into it...

[Sebmaster]

While I do agree that we should move that kind of thing into the parser as far as possible, this problem doesn't stem from jsdom.

I'd expect the htmlparser2 tree-adapter to produce the same output format as htmlparser2 itself, however apparently this is not the case.

[Sebmaster]

Oh well, thanks @fb55, had more time to look into it just now. Seems like we can drop our custom HTMLDecode function and use htmlparser2/parse5 for that. Thanks!