Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

On SO, I made a comment and realized I'd written 'and' where I meant 'any'. The timer said '4 minutes', but the edit option was still present, so I tried to edit it; it wouldn't let me save it - even though it still said '4 minutes' when I had cancelled it.

Why was the edit option present when it was no longer valid?

And, more particularly, can 'you' (the SO team) do something so that people do not waste spend time editing a comment when the edit will not be accepted.

share|improve this question
Are those air-quotes around you? – Peter Ajtai Aug 26 '10 at 21:44
up vote 5 down vote accepted

The edit window is 5 minutes, but the text that says how long ago the comment was made is generated by the webserver and not updated live by javascript.

If you see that a comment was posted 2 minutes ago and come back 1 hour later the edit button will still be present and it will still say posted 2 minutes ago.

share|improve this answer
OK - but it would be kinder to the user to include in the information available to the client-side JS the actual time that the comment was made, so people aren't allowed into the editor if the result will not be savable. I can see that requires some changes - but changes is what I'm asking for. Don't let people spend time editing when their effort will not be accepted. That's nasty - or, if that's too strong, it is not as pleasant a user experience as could be provided if the JS knew when the edit window would close. – Jonathan Leffler Aug 26 '10 at 21:32
@jon Once you bang your head against it few times, you get into the habit of refreshing before editing a comment that is not recent. Refreshing before posting is certainly a good habit. Not that I disagree with you, it could be a smoother user experience. However, I think the dev team has bigger fish to fry. – George Marian Aug 26 '10 at 22:49
If you update some data in real time, it might start to get confusing as to whether a particular piece of data is or isn't. – Gelatin Aug 27 '10 at 0:29
@Simon: exactly; if it's not done with EVERYTHING it's just confusing. And it's confusing even if it's done with everything as not many websites do it. I don't think it's a very good idea. – Andreas Bonini Aug 27 '10 at 2:24
@George: I don't like repetitive head banging - I was never a heavy metal fan. – Jonathan Leffler Aug 27 '10 at 10:57

It checks on POST whether or not the edit is valid. So when you loaded the page, you were 4 minutes after and editing was still a valid option.

* * * Time passed. * * *

Then the edit is no longer valid (the edit window has passed), but the page has not been reloaded and so it still shows the state that it was at on your initial load.

share|improve this answer
So now we know the technical reason for the misfeature. Now let's do something to fix it! – Jens May 29 '12 at 22:47

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .