2 Answers
2

Well, since comments won't allow the ordinary strike formatting, someone there tried (and succeeded!) to trick the system by combining Unicode characters resembling English letters with a strike through them.

This results in one long stream of characters without any blank space, no different than:

If you run the above through an ASCII converter (this one was built from scratch just now, as I didn't find any decent converter online) you will see there is no blank space but rather a character with ASCII value 822 following each letter.

The common thread in all these bug reports is that they involve some kind of an over-wide unbreakable block of text in a comment, which causes the table that contains the comments to extend to accommodate it, overflowing out of the main content area and into the sidebar.

There's a simple CSS fix that (mostly) solves this bug: just set an explicit max-width on the comment text cells:

This will cause any over-wide comments to stay within their prescribed bounds, breaking long words if necessary, and acquiring a horizontal scroll bar if even that doesn't help, like this:

(The padding-right: 2px kluge is a workaround for what appears to be an uncommon Chrome bug causing the horizontal scroll bar to appear even for comments that are not over-wide. Basically, Chrome's layout algorithm seems to sometimes mis-estimate how wide the table cell should be, and ends up making it one or two pixels too narrow; the extra padding appears to give it enough slack to accommodate such mistakes.)

Ps. This fix is include in the latest version (v1.22) of the Stack Overflow Unofficial Patch user script. (Earlier versions had a slightly different fix, which used table-layout: fixed instead.) The word-wrap: break-word feature will be added in SOUP v1.30. (It's already present in the v1.29 devel branch.)