2

Glancing at an old answer of mine, I noticed that in one of the two code blocks, \\ is converted to \ and the following line break is ignored. In the other, the \\ is not immediately followed by a newline, and it appears as written.

I believe this differs from what the web interface shows: both of them should actually show up as \\ (although it's possible the Markdown semantics changed since the answer was written).

Example 1 \\
Next line

vs.

Example 2 \\more stuff
Next line

(After posting, I notice the above examples don't behave the same way, perhaps because the lines aren't long enough.)

screenshot

  • App Version: 1.6.2.5
  • Device: iPhone 7
  • OS Version: Version 10.2 (Build 14C92)
  • This doesn't appear to be iOS specific. I see the same behavior on desktop. Also, if I go in to edit the answer, the code block matches the rendered markdown (no line break, one backslash). – Brian Nickel Jan 20 '17 at 17:54
  • It seemed suspicious that my examples in this question don't exhibit the problem when viewed on iOS. – jtbandes Jan 20 '17 at 20:23
  • Wow, you're right, the source given when starting an edit does match the rendered output. Maybe a bad migration at some point in history? – jtbandes Jan 21 '17 at 7:54

You must log in to answer this question.

Browse other questions tagged .