KillyMXI

No idea why you run into this issue. `htmlparser2` [still exports](https://github.com/fb55/htmlparser2/blob/master/src/index.ts#L74) `DomHandler` as `DefaultHandler` and that shouldn't cause any issue. This might be related to how your web project is...

This particular example doesn't reproduce in version 7. [htmlparser2](https://github.com/fb55/htmlparser2) got smarter recently and doesn't consider `

You know what? Even Blink (Chrome's engine) is confused by `

Ok, now I'm pretty confident there is no parser to switch to in order to address this issue. contains most of the ones worth looking, and I made a PR...

@sairupesh I can't reproduce this. Sounds like you're unescaping html somewhere in your pipeline before calling html-to-text. ```js const text = htmlToText( ` Point 1 - this is point 1...

Sorry for the late reply. Yes, you got it right. Existing behavior is motivated more by the ease of implementation than by any specific usage scenario. Trying to fit an...

Hi, thanks for this question. Interesting use case. Currently there is only an option to specify `maxColumnWidth` for tables. It will wrap anything that exceeds the given value but still...

@Sun3 Columns? I was working on some part of this issue in December, until my laptop broke. I've also discovered back then that I have to rewrite quite a lot...

It is not as easy as it may sound. Text is not HTML. You rely on HTML to present the examples for your issue. To represent super~ and subscript in...

This is pretty useless without the input string that caused it. (You might not need to share the exact data you working with. Depersonalized data that still triggers the issue...