Dave Wichers

It's possible this isn't a Windows specific error. Here's a run on GitHub with this same failure: https://github.com/nahsra/antisamy/actions/runs/3498387502/jobs/5858682120 with: but: was , rather than: but: was . Maybe this is...

WSL? What is that? I have no failures on my Mac. This error is definitely not repeatable. It just shows up, sometimes ...

@spassarop - Can you research and possibly propose a fix?

@BloodDrag0n - The fix for this will go out in the 1.7.5 release, which hopefully will be this week.

This was fixed in the 1.7.5 release.

@spassarop - Are we going to do anything about this? Or did you already, like add notes to the README or something?

@spassarop - I tested the new 3.11.0-SNAPSHOT and AntiSamy fails 3 tests like so: [ERROR] Errors: [ERROR] AntiSamyTest.issue37:1002 » Scan org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified....

@kwwall @spassarop - what is the status of this PR? Close it, work still to be done, ???

@spassarop - do you want to propose an update to the README and then we can merge that and close this issue?

I'm sure its possible, and its probably a good idea. We just haven't made it a priority. If you have some experience doing such rewrites of XML parsers any chance...