Just happened to me again and I didn’t have multiple tabs open, so I think it’s a bug. Both times the page I saw after submitting was the post I’d intended to comment on, but my comment wasn’t there.
I think this may be a thing where LW stores your comment in local memory (so if your computer crashes or the site reloads due to a new version deploy, you don’t lose your comment). I think comments that are parented under a comment get stored properly as a reply to that comment, but maybe global comments get stored as “truly global” rather than parented under a post.
And then maybe when you go to a new post, it keeps the old half-written comment, making it easier to accidentally po?
(Except that I just tried to replicate this on purpose and couldn’t get anything to happen, so maybe this is just wrong. But maybe points in a useful direction?)
I am actually just debugging a similar problem for private messages. Will try to replicate it for comments.
(Basic idea is that we persist the new-comment form between page transitions, and there is a bug where some of the properties of the form don’t properly propagate, and this might sometimes result in you being on a new page, with a form that still has the properties of the old page)
Just happened to me again and I didn’t have multiple tabs open, so I think it’s a bug. Both times the page I saw after submitting was the post I’d intended to comment on, but my comment wasn’t there.
I think this may be a thing where LW stores your comment in local memory (so if your computer crashes or the site reloads due to a new version deploy, you don’t lose your comment). I think comments that are parented under a comment get stored properly as a reply to that comment, but maybe global comments get stored as “truly global” rather than parented under a post.
And then maybe when you go to a new post, it keeps the old half-written comment, making it easier to accidentally po?
(Except that I just tried to replicate this on purpose and couldn’t get anything to happen, so maybe this is just wrong. But maybe points in a useful direction?)
I am actually just debugging a similar problem for private messages. Will try to replicate it for comments.
(Basic idea is that we persist the new-comment form between page transitions, and there is a bug where some of the properties of the form don’t properly propagate, and this might sometimes result in you being on a new page, with a form that still has the properties of the old page)
Yep, replicated it. Fixing it right now. Sorry for that happening.