Based on your now reverted edits on your original question, and the comment chain on that question (that hopefully will be cleaned up soon), you seem to have a view that the presence of a tag (and the description in the tag wiki) are evidence that questions are on-topic.
Well, that is not a true statement. With only 500 rep needed to create a tag, bad tags are created frequently, and once a tag is created, there is nothing to stop someone from creating a tag wiki (except 3 reviewers). In fact the presence of another similar question is not even evidence that a question is on-topic as that question might not have been closed yet.
On-topic questions are still based on the "What to Ask" and "What not to Ask" sections of the help center.
Your question, while it is about a software tools commonly used by programmers, fails the final criterion for "what can I ask":
- practical, answerable problems that are unique to software development
The reason is it is not answerable. The only person that can reasonably answer that question is a developer for the particular tool because you aren't asking how you can see older versions, you are asking why you can't see a specific version. This makes it a support question and better suited for the developers for jsfiddle.
You also seem to be hung up on the fact that the question was closed for the wrong reasons. In that sense, you are only partially correct. It takes 5 votes to close a question (and it is 5 votes for any reason, not 5 votes for the same reason). Because of that there are frequently conflicts in what the close reason should be. Normally the majority rules so you'll never see a close reason with just 1 or 2 votes unless it was the most selected reason.
In your case only 2 close voters actually picked the "Recommendation" close reason. 3 other people appear to have picked a slightly more accurate custom close reason "This question is off-topic because it is about jsfiddle." Since both of the selected reasons are sub-categories under the "Off-topic" close reason, you are shown both. And because the majority reason is a custom close reason, it is not shown in the banner message, but instead in the comments.
But in the end, the question still needs to be closed as it is not on-topic and the community has shown a preference to leaving questions closed with incorrect reasons as the effort to reopen an question and reclose it with the correct reason is better spent in other moderation tasks (such as the 91K+ questions in the close vote queue).
If you ever encounter a post that is closed for a reason that is just so off-the-wall wrong, you can flag it for a moderator's attention and explain that it should be closed for a different reason. NOTE: This question, I don't think qualifies since it close reason, while not accurate, is not dangerously misleading. Usually the best use case for flagging to change close reasons is when it closed as a duplicate of a post that is not even close to being a duplicate, but the post still should be closed.
This question appears to be off-topic because it is about jsFiddle
. And I agree. This sounds more like a support question for jsfiddle than a programming problem