The multicollider seems to have taken upon itself to partially escape apostrophes and break itself:

enter image description here

Code behind it: enter image description here

The actual comment (with code): enter image description here

Minor, but it's still a . OK, it's more of a

Testcases from comment spam below

The "character" referred to is the escaped one.

  • Original case: Thanks for the Screenshot. I'm not sure if the site will allow me to post one yet as it won&#... (92nd character)
  • This comment: '''''''''''''''''''&#... (20th character)

closed as off-topic by Adam Lear Oct 17 '14 at 20:47

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "The problem described here can no longer be reproduced. Changes to the system or to the circumstances affecting the asker have rendered it obsolete. If you encounter a similar problem, please post a new question." – Adam Lear
If this question can be reworded to fit the rules in the help center, please edit the question.

  • It seems like this will only happen when the apostrophe character is in exactly the right pos I'd wager – Some Helpful Commenter Apr 6 '12 at 16:04
  • @ConradFrix: Yep. My multicollider did it again on your post.. Feel free to start testing various apostrophe positions here (I don't mind getting my inbox spammed) ;) – Manishearth Apr 6 '12 at 16:06
  • 5
    "partially escape apostrophes" seems rather unlikely. The problem is it escapes characters and then truncates for the inbox preview; it should do them in the opposite order – Michael Mrozek Apr 6 '12 at 19:36
  • I noticed this too. – kiamlaluno Jun 30 '12 at 23:08
  • 1
    +1 for the beautiful handwriting on the screenshots – wchargin May 7 '13 at 3:31

Given that the multicollider does not exist in the current build of our network sites, I cannot reproduce this issue. Please let me know if you experience similar issues with the current top bar.

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