Sometimes when adding a comment to a solution I get a massage saying "We have tried to update your comment 3 times without success. Our servers...". That's okay, but what happens is that the comment is lost since the text box for the comment disappears when the Submit button is pressed. When adding a solution the situation is different and in case of an error the solution box remains.
Could the editable comment box have similar behavior (not removed until the submit has succeeded or message cancelled by user)?
I moved some code from a comment to the question section in this question[^], but despite all my efforts I cannot get the indenting to work. If you edit the code section you can see the spaces at the beginning of each line.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
I one voted an article because I thought it was bad but then realized the author had made references to the shortcomings. The references were hard to spot earlier. Anyway, since I couldn't take back the vote, I changed it to a three. I would have preferred to cancel the vote because that didn't deserve any up votes.
Partly. The requirement to post a comment with a low vote also played a part of course. I only ever vote 1 or 5, and hardly ever a 5. I found myself voting 1 and then the article would be improved, but not to a 5, and I couldn't remove the 1. So I stopped voting on articles altogether and just report the really bad articles and/or write a comment.
Even if I could remove a vote, going back and reviewing my 1s would be tedious and I probably wouldn't bother. I think it would require an email notification that an article I had 1ed had been updated.
I think it would require an email notification that an article I had 1ed had been updated.
This should happen anyway IMO - at least by default with an opt out user setting. If the article has changed substantially then the down vote may no longer reflect the quality and should either be removed or recast.
OK, that makes sense. I thought it was the awful sense of finality that was causing you grief.
"Do I vote? Do I not vote? If I vote a 2 will I regret it later? But I don't want to vote it a 4 because it's not good enough. Oh, if only I could vote it a 2, just for a day, then take it away, rest, and then, maybe, vote a 3 the following day."
So it's more about having your vote stay relevant to the article as the article changes.
That is something I can definitely add to the TODO.
Thank you for this reply. After some more observations, it looks like modified "br". A line break automatically adds a "br" tag, as it probably was before. I checked it up on my old posts. Maybe new code is better, because repeated line break is accumulated in just one "br" break (is it so? you could check it up, as to test it I would need to create a fake question/answer and remove it).
The only problem is that before "br" was probably rendered by a style with 1 em vertical interval (margin), and not it is not.
Could something be done to preserve old rendering of the past posts, as those posts are used, referenced, etc.?
P.S.: to make this post rendered properly, I've used "p" tags. It would not be a problem; the problem is rendering of past posts designed to the old rendering style.