-
Because unicode.
@psee had two
&8235;
characters at the start of his username, and these are the "right-to-left embedding" characters: http://www.fileformat.info/info/unicode/char/202b/index.htmI escape these and Chrome correctly doesn't do anything with them, but Firefox and potentially other browsers were not doing the right thing and were actually partially parsing them.
The partial parsing would lead to some unicode spilling onto the page and moving the word to the right side of the line.
This is actually already fixed, in that I fixed it two months ago: https://www.lfgss.com/conversations/131364/?offset=5575#comment12687864
Non-printing unicode is no longer allowed in usernames.
I had chosen not to retrospectively apply that filtering though as I didn't know of a place in which actual harm occurred as a consequence. Well, now we have an example I've changed psee's username to remove the non-printing unicode and it all works fine again in the browsers that were incorrectly parsing the escaped characters.
Because of ignore lists.