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
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:
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.