Closed GoogleCodeExporter closed 9 years ago
Forgot to include this information:
This problem does not exists in the DOM parser as far as I can tell
Original comment by arthur....@gmail.com
on 3 Aug 2011 at 9:27
I took at a look at the source code from /tags/Java/antisamy-project-1.4.4
(latest release) to see if I can fix this.
I found that AntiSamySAXScanner does not honor the "useXHTML" flag in the
policy files. So when it is creating the transformer it is always using "HTML"
output instead of "XML" when "useXHTML" is true.
I made a patch that fixes the issue. However there are failures when I run the
unit tests and I don't know enough about the tests to make changes to them.
I have attached the patch for AntiSamySaxScanner if someone can apply this and
update the test cases that would be greatly appreciated.
Original comment by arthur....@gmail.com
on 4 Aug 2011 at 7:50
Attachments:
Fixed in HEAD. Thanks! The XHTML directive was ignored in SAX, unfortunately.
Original comment by arshan.d...@gmail.com
on 14 Sep 2011 at 8:55
Original issue reported on code.google.com by
arthur....@gmail.com
on 3 Aug 2011 at 9:01Attachments: