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.)
(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.)
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.)