3

Occasionally when posting a comment I find that the @username that I generally put at the start gets dropped when I save it. This is normally correctable by editing and re-saving the comment. Somewhat annoying but not the end of the world.

Tonight I was posting a comment to this question and despite twice editing and re-saving it, the "@Frerich" that I was trying to put at the beginning just kept getting dropped. I gave up at that point.

Using Google Chrome version 22.0.1229.79 on OS X 10.8.2 (Mountain Lion), with all updates applied.

3

This, to the best of my knowledge, is actually . In this MSO thread, it says that as you could only be replying to the person that asked the question (in your example) then the @Username is stripped out automatically. If you can fully understand that answer in its entirety I would be more than impressed as it's not exactly clear.

  • I'm sure you'll understand if I don't bother to read anything that justifies such absurd design. Thanks for the answer. Of course that doesn't explain why I can normally edit the name back in. – John Gardeniers Oct 2 '12 at 9:59
  • And now I have to wait another minute before I can accept your answer. Gotta love devs who understand UI design. :/ – John Gardeniers Oct 2 '12 at 10:00
  • 1
    To be honest, I don't think it's justifiable, apart from "to reduce clutter and noise" or to save some precious database bytes. – tombull89 Oct 2 '12 at 10:02

You must log in to answer this question.

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