The Close Reason Editor allows you edit the off-topic close reasons which are normally editable only by the site moderators.

Close Dialog

Show or hide the default off-topic close reasons

If, for some reason, you do not agree with the default close reasons, or you rarely need some of them, you can hide* them from the close dialog by deactivating them.

*: They will still show up in the close dialog if someone else has already chosen that reason for that particular question.

Default Off-Topic Close Reasons

Save your favorite custom off-topic close reasons

You no longer have to type your most commonly used close reasons over and over again. Simply save them once, and you can use them just the way you want.

Custom Off-Topic Close Reasons


  • You need to have the "cast close and reopen votes" privilege (3000 reputation on graduated sites) in order to use the custom close reasons.
  • You have to use a browser that supports localStorage.


  • 1
    +1, awesome! I'd thought about writing a script to do something like this myself, but now I don't have to! :-) And the user interface you've got is incredibly polished. Commented Feb 18, 2014 at 22:02
  • Now make one where I can see instantly who is on-line (not in the Chat room) but in the Q&A.
    – Ruskes
    Commented May 22, 2015 at 5:40
  • I use this a lot now at PPCG. My Custom VTC is for incomplete challenges. Commented Jul 4, 2016 at 18:56
  • I assume this project has been abandoned? I've downloaded this quite some time ago and have always encountered the same result when attempting to add custom reasons. Commented Nov 24, 2018 at 0:46
  • @K.Dᴀᴠɪs I am sorry. I haven't been maintaining this script because I am not actively using the site these days. I will take a look at this if I do manage to find some time to debug it, but I can't promise anything. This script is open source however so other people can take over if they want.
    – Antony
    Commented Nov 26, 2018 at 2:47
  • @K.Dᴀᴠɪs I have fixed the problem and updated the script. StackExchange updated the topbar at some point and broke the script. Please click the download link for the latest version of the script and let me know if this works now. I am sorry to keep you waiting all this time. In the future, please post a bug report as an answer and I will try to fix it whenever possible.
    – Antony
    Commented Nov 26, 2018 at 3:39
  • You're awesome! Works perfectly now, thanks for the ping! :) Commented Nov 29, 2018 at 23:26

2 Answers 2


I ran into a problem, using Firefox ver. 38...

The adding of Tags to a new question initiates a scripting error and does not let me add tags.

If I turn off the close-reason-editor I am back to normal.

When I try to ask new question, and click on add tags, I get the Firefox to freeze with spinning beach ball followed by Error message.

This is the output:

Use of getAttributeNode() is deprecated. Use getAttribute() instead. jquery.min.js:2:0
Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. jquery.min.js:3:0
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] qa.sockets.stackexchange.com
Error: Script terminated by timeout at:

enter image description here

  • Can you open the JavaScript console and post the error message here? And what do you mean by "adding tags to a new question"? Are you on /questions/ask, /posts/{id}/edit or /posts/{id}/edit-inline?
    – Antony
    Commented May 24, 2015 at 14:41
  • I am unable to reproduce the issue on Firefox 38 on a Mac on the "Ask Question" page. Please refer to this post on how to open the JavaScript console, and include relevant details in the bug report, e.g. the error message you see in the console, the URL of the page you where encounter the problem, a screenshot of the error, or any other information that may help explain the issue.
    – Antony
    Commented May 26, 2015 at 2:19
  • Will do, I removed the script since it was bugging me. Now I have to install it and report. Might be a while :)
    – Ruskes
    Commented May 26, 2015 at 2:25
  • @Antony OK, installed and running, nothing so far.
    – Ruskes
    Commented May 26, 2015 at 2:29
  • Thanks for the report. The bug has been fixed. Please update the userscript to the new version.
    – Antony
    Commented May 26, 2015 at 14:17
  • I had the same thing (haven't tried the updated script yet). Were you also getting a confirmation dialogue each time you attempted to post a question or answer?
    – terdon
    Commented Sep 16, 2015 at 14:31

This script caused me both the bug reported by Buscar and the one reported here (I was asked to confirm leaving the page each time I posted a question or answer).

Removing the script solved both bugs and, since I don't really use it, I can live with that. I won't be following up on this but I thought it was worth reporting.

  • This is probably related to wmd.en.js being loaded twice. I have fixed this in the latest version of the script. Can you please update it to test it for me? I know you don't really use it, but making sure this is fixed properly would benefit those who do use the script.
    – Antony
    Commented Sep 16, 2015 at 16:16
  • @Antony I did try the new version you have in your answer before posting this. I still had the confirmation bug. Let me know if you update it again and I'll give it a go.
    – terdon
    Commented Sep 16, 2015 at 16:44
  • Are you using version 1.1.5? I just updated it an hour ago.
    – Antony
    Commented Sep 16, 2015 at 17:09
  • @Antony oh, sorry, I was looking at the time the OP was edited. OK, I'll try this tomorrow (no time now).
    – terdon
    Commented Sep 16, 2015 at 17:14

You must log in to answer this question.

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