Then we have a problem with discourse.
I will investigate.
Thanks
@sourav can you explain why using the reply button on a particular item does not show up as a pointer to who it is replying to .
It normally doesnt show if the reply immediately follows the item, but this case was replying to an item way back.
It seems to work sometimes, but not always … a real beast to track.
eg reply 74 has no pointer, but reply 80 has a pointer.
Here is why the reply pointer (the little arrow and avatar in the top-right of a post) sometimes seems to disappear or act unpredictably on Discourse:
Post-Level Reply vs. Topic-Level Reply: If you click the Reply button directly under an individual post (e.g., #74), Discourse attaches a pointer linking back to it. However, if you read #74, scroll down, and click the big Reply button at the bottom of the thread, Discourse treats it as a general reply to the topic as a whole—so no pointer is added, even if you are responding to #74.
Immediate Neighbor Suppression: If you reply directly to a post and your response lands immediately below it, Discourse automatically suppresses/hides the pointer to reduce visual clutter. If someone else posts in between while you are typing, the pointer suddenly becomes visible because it’s no longer directly below.
Minimizing or Switching Drafts: If you click “Reply” on post #74, minimize the composer box, click around, or use quote buttons from other posts, the draft system can sometimes clear or override the target post metadata before you hit Submit.
The Golden Rule: To guarantee a pointer back to a specific post far back in the thread, always use the Reply button attached directly to that specific post, and avoid clearing or minimizing the draft before posting!