5

This question on TSE was marked as duplicate on 2016/02/24 at 15:52:19Z. It was then answered on 2016/02/24 at 15:52:52Z, seconds after being marked as duplicate.

enter image description here

How is this possible? Is there a delay between duplicate marking and closure? If so how long is this delay?

3
  • There's a delay between the closure and when answers can no longer hit the button. (I don't remember how long it is.) There is also a delay between closure and when the server will stop taking answers, in case someone re-enables the button by messing with the css in their dev tools. That I know is 4 hours.
    – Kendra
    Feb 24, 2016 at 16:08
  • @ShadowWizard The irony.
    – Mithical
    Feb 24, 2016 at 17:19
  • 1
    @Mithrandir it could be ironic if Patrick posted the answer after this was closed, but alas, that's not the case. :) Feb 24, 2016 at 17:26

1 Answer 1

3

That is possible since you are allowed to submit your answer if you started typing before it was closed as duplicate. This allows answers to come in minutes or even hours after it was closed. If you were connected it will disable the commit button but that can easily be reversed with some browser tools.

In my opinion, this is bad design, especially since it encourages bad answers to come through on rapidly closed questions.

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