workaround is to call Trim() prior to GetSafeHtmlFragment()

The strange think is when i do this:

Sanitizer.GetSafeHtmlFragment("1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890");

The output will be:

"1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890 1234567890\r\n 1234567890"

It add a carriage return, when the text is longer it will add more carriage returns

I am also seeing this issue, but it doesn't have to be for text that end in a white space. If the text is long enough it adds in random carriage returns everywhere.

I also have the exact same problem as erwin118! It seems to add a line feed at the first space after 256 characters.

The answer to the long string problem is answered here (http://stackoverflow.com/questions/9942751/asp-net-html-sanitization-library-adding-line-feed-after-256-characters). Just replace all newlines with a marker string, do the sanitation, remove all newlines that have appeared and the replace the newlinemarker with real newlines.