Please don't do this. In the event of a network failure, this can leave one unable to retry submitting a comment; I have actually experienced this on sites other than LW.
Instead, assign a unique identifier to each created comment form, and if the server receives two submissions with the same identifier, consider the second one an edit to the first comment. (Even client-side pseudorandom identifiers would be good enough for these purposes.)
Exactly!
(I thought that this was how LW already worked. My impression was that the code for replying to comments still has such a system and it is just the replying to the original post that is broken.)
I saw some discussion posts earlier talking about a LessWrong redesign, and now that things look different, I guess that it's been implemented. I'm always slightly annoyed for a while when a site I use gets redesigned because I have to relearn where everything is, but it eventually wears off once I'm used to the changes.
My initial impressions:
"Hmmm... it seems like the category menus have been replaced by dropdown menus. It's not like I used many of them anyway."
"Okay, I've clicked my name to see my recently posted comments. Now, where's the link to see it in context? Oh, I guess I have to click that icon in the lower right corner. For some reason I was looking for something at the upper right of the comment box."
"Well, that worked. Now how do I click to the parent comment? Oh, wait, it's probably one of those new icons in the lower right corner. I'll just mouseover them to see what they do..."
::realization sets in::
"AAUGH! LESSWRONG IS USING MYSTERY MEAT NAVIGATION!!!"
So, what does everyone else think of the new redesign?