Invalid HTML error if the content contains special characters (<3)
Closed this issue · 2 comments
mrdeeds88 commented
mrdeeds88 commented
I was fixed this by pre-format the content before parse it to clipper.
arendjr commented
Yeah, I would say this is by design, since "<3" should be encoded as <3
to be valid HTML. I suppose things could be made a bit more resilient by implementing the fallbacks that HTML5 specifies for invalid HTML, but I'm afraid that would add a huge amount of complexity to the library.
So I'm closing since you found a workaround. Thanks for the report, it's indeed something to be aware of!