Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 153 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

This question already has an answer here:

Recently, (on meta), I was able to answer this question 30 seconds after it was closed.

Close time:  2013-12-05 02:37:22Z
Answered at: 2013-12-05 02:37:52Z

This is fine. It is not a bug, rather it is as pointed out here.

While answering the question, there seems to be an interval in which (web sockets?) check if a question has been closed or not. If the check returns true, you are presented with the following message:

(Related to this question, asked 4 years ago)

This question has been closed - no more answers will be accepted.

After closing some questions, I found that the interval seems to be under 1 minute.
(I got ~22 seconds, ~49 seconds, and ~13 seconds when testing)

In other words, if you are typing an answer to a question, you have less than a minute to submit your answer - assuming the question has been closed. You will then be presented with the message above and the submit button will now be disabled.

<input id="submit-button" type="submit" disabled="disabled">

There are no evident problems with this. It seems to work well; however, if you edit the HTML and remove the disabled="disabled" attribute, you can bypass this and submit an answer.

Here is an example on SO where I did this. (10k users only - I deleted my answer)

Close time:  2013-12-05 19:11:28Z
Answered at: 2013-12-05 19:41:06Z

By removing the disabled attribute, I was able to submit an answer ~30 minutes after the question was closed.

Should this be allowed or not? In this comment from Jan 2011, Jeff points out:

the grace period for answer submission is now 4 [hours] after after question closure

Yes, the quote does say after twice.

Despite the fact that this comment was written ~3 years ago, there is still a 4 hour grace period in place. After sitting on a particular answer for ~5 hours, I failed to submit an answer and was presented with the following:

This grace period is intended for people already answering a question before it has been closed. So why is the submit button immediately disabled upon being notified that the question has been closed? This defeats the entire purpose of a grace period. Especially since it can be bypassed.

share|improve this question

marked as duplicate by Mołot, hims056, Martijn Pieters, Azik, Aziz Shaikh Dec 6 '13 at 9:33

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Discussion or bug? Why not both :) This most certainly is a bug that can be very trivially exploited. – Madara Uchiha Dec 5 '13 at 21:20
What kind of server-side check would you possibly be able to implement? If you allow a client-side grace period, users will always be able to bypass it with tricks. 4 hours is an excessively long grace period. I'd say drop it down to 5 minutes. – animuson Dec 5 '13 at 21:22
@animuson: Actually, there is a server-side check. It didn't work for a very long closed question.. – Madara Uchiha Dec 5 '13 at 21:28
@animuson Well, my question is questioning whether there is actually a grace period. The server side check would just check if the question is closed or not; thus preventing this. Why is the button disabled if there actually is a grace period? And yea.. 5 mins sounds very reasonable. It would be ideal to have a server side check implemented to check time passed before submitting. – Josh Crozier Dec 5 '13 at 21:28
@JoshC I thought you meant some sort of server-side check to determine if their button has been disabled. I'm pretty sure it already checks the question's close time to the current time. I'd say it's safe to assume that allotment is still 4 hours (which again is absurdly long). – animuson Dec 5 '13 at 21:30
I believe the grace period, though, was meant for users who did not have JavaScript enabled or for some other reason could not be notified that the question is now closed, so they continued typing not knowing that fact. – animuson Dec 5 '13 at 21:31
@animuson Yes, that's why. See this answer by Tim Stone. – doppelgreener Dec 6 '13 at 3:48
up vote 3 down vote accepted

There is a server side check.

I tried with Tool for Converting Visual J# code to C#?, it doesn't work.

Sure, it's silly to say there's a grace period of 4 hours on the one hand, and then disable the button immediately on the other hand. That could be the .

share|improve this answer

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