Hello @boutell, this is another PR as asked by you. It has only the change which was needed for the issue.

Test cases were changed to bring the behavior in sync with the new version of htmlparser2.

Please let me know your comments and changes needed.

Thanks,
Kedar Chandrayan

Because of the parser option, which is passed on directly to htmlparser2, it is a backwards compatibility break to upgrade to a new major release of htmlparser2, unless the htmlparser2 API has not changed. Can you review the changelog of htmlparser2 to figure out if we need a major version bump for sanitize-html itself and/or a few bc wrappers to allow legacy htmlparser2 options to still work?

@kedarchandrayan reminder that there is an unanswered question blocking this PR:

Because of the parser option, which is passed on directly to htmlparser2, it is a backwards compatibility break to upgrade to a new major release of htmlparser2, unless the htmlparser2 API has not changed. Can you review the changelog of htmlparser2 to figure out if we need a major version bump for sanitize-html itself and/or a few bc wrappers to allow legacy htmlparser2 options to still work?

Sure @boutell, I will go through the CHANGELOG of htmlparser2 for figuring out the need for a major update here. Sorry missed your last reply.

Hello @boutell, htmlparser2 has src/Parser.ts which has interface ParserOptions for the parser options. The properties in this interface are the same in versions 6.0.0 and 8.0.1 (latest). So there is no change in the options.

Additionally, I went through the release changes mentioned here. Parser option change is not mentioned in any release.

Conclusion: We will not need a major bump for this PR.

Thanks!