I totally agree.
There were discussions in the past, like in Close vote review audit flawed - fails without casting vote, where the accepted answer is by Shog9, who said
I consider this behavior appropriate for most of the audits. If you're clicking "close", you probably do want to close the question.
However, it kinda falls apart when you want to close a known-good question as a duplicate.
Fixing this would require dragging in code that's currently being extensively re-written; doing so is not feasible at this time. It may or may not become possible in the future - even without the current re-write, the logic for that UI isn't trivial to fake.
Such answer is legitimate, but clearly the community didn't find it satisfying as it received several downvotes.
I strongly believe testing only the press of Close is not doing any good, and this is a good example. Also I can think of the case in which a unexperienced reviewer is deciding whether to close a post, she hits Close and then she realizes that none of the close reasons apply and therefore decides to leave it open. That's a good behavior, and exploring the close reasons is a great way of learning how to be a good moderator.
should rather be
- hits close → none of the close reasons apply → closes for the wrong reason → bad boy!
- hits close → none of the close reasons apply → leaves open → good boy!
- hits close → closes the question as duplicate of itself → good boy!
According to the answer given by Shog9 this wasn't feasible at that time (May 10, 2013), since there was some code being extensively re-written. Now it has been a few months since then and I wonder whether the time has finally come.