On this answer, it looks like the user entered some arabic text, and it caused the comment text and the timestamp to switch places.
Getting mixed LTR and RTL text to play together nicely is difficult. The comment is in Arabic, and the numbers then stay in RTL (because there's no way for the renderer to know if they're part of the RTL text or not) until the renderer sees text that must be LTR. It might work better if SO emitted a Unicode LTR shift before its boilerplate.
While this bug has been partially fixed by adding the
One way to fix this issue would be to forbid RTL text (or at least RTL control characters1) in comments. However, that would be throwing the baby out with the bathwater — there are legitimate reasons for writing, say, Hebrew or Arabic text in comments, and indeed there are some SE sites (like, say, Mi Yodeya or Islam) where such comments may even be fairly common.
Instead, the proper way to fix this issue is to isolate the directionality comment text (and the username) from the surrounding elements using the
Unfortunately, browser support for this relatively new CSS feature is still quite limited, so, for the time being, we're also going to need some vendor prefixes and a fallback to
With this CSS rule, the comments shown above look like this:
(This rule will also be included in the next version of the Stack Overflow Unofficial Patch user script.)
1) I would, in fact, support the blocking / filtering of the Explicit Directional Override characters LRO (U+202D) and RLO (U+202E) in comments, since they have very few if any legitimate uses and a high abuse potential. Even the Unicode consortium nowadays says that "they are to be avoided wherever possible, because of security concerns."