This situation will potentially be hard to recreate, but there is a question on Arqade that when editing changes spaces (Space) into hard enters/line breaks (Enter).

It happens when editing this question on Arqade. When editing other questions it does not happen. Another user corroborated the occurrence (if necessary, I can share my soft- and hardware specifications, but since someone else was able to reproduce it, I think it is a server-based (?) bug (?)).

It only happens when editing anything after the two first lines (the first being an elliptic comment, the second an empty line).

Does anyone know why or how this happens? Is it a certain (string of) character(s) that might be responsible?

1 Answer 1


Saving the revision source (downloadable here) and opening it in a text editor immediately identifies the problem:

I created a typical game captures the flag but I have a strange bug. If I am the 1st player to enter the game (me=player id1) the game works well all players can respawn. But if another player comes before me and I have id=2, then the other player dies and stays in respawn(0sec) all the time.

The entire post has been written using non-breaking spaces (spaces which will not result in the line splitting and wrapping). As a result, whenever you add a real space, that space is a new place for the post to wrap correctly.

You can fix this by simply copying the entire contents of the post, and re-pasting it. That should replace all non-breaking spaces with normal spaces.

You can see the result of editing the spaces to normal ones in the markdown view of an edit:

Image showing side-by-side markdown view of revision to the post in question. All spaces in the post are marked as having been removed and re-added as they were replaced with a different type of space.

  • That explains a lot, thanks! I thought it might have been something like that, but couldn't switch the editor view, and figured these spaces would be removed automatically when posting something (for some reason).
    – Joachim
    Feb 2 at 10:51
  • 2
    @Joachim Yeah, the issue was pretty clear, proving it was less easy because every time I copied the text into a character checker all the spaces got fixed. Ended up having to open the revision history (/posts/<id>/revisions) to get the source link to download it. Feb 2 at 10:52

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .