30

If a bounty is active on a question, that question cannot be closed. However, attempting to vote to close works just fine until the "Vote to close" button is pressed. Only then does the "this question has an active bounty and cannot be closed" message pop up.

There may be a technical reason for this, but there's no workflow reason for it. Please show the message as soon as the "close" link is clicked.

3
  • 1
    I just cant do it.... – Naftali aka Neal Jun 6 '12 at 15:20
  • There is (nowadays) a workflow reason of sorts: if some users have voted to close the question before it was bountied, clicking the "close" link to open the popup lets you see which close reasons they picked. However, we could still support that use case by opening the popup, but e.g. replacing the submit button with a big red notice saying that the question cannot currently be closed. – Ilmari Karonen Nov 26 '17 at 0:21
  • What about hiding the "close" button altogether? – iBug says Reinstate Monica Jan 24 '18 at 0:58
1

As of v1.50, my SOUP user script now contains an implementation of this feature.

The way I implemented it is by detecting the presence of the bounty notice on the page and, if it's there, disabling all the radio buttons in the close popup that don't open a submenu. This should make the dialog obviously and visibly non-functional (and also impossible to submit, since you can't actually select a close reason), while still preserving the other functionality of the popup (i.e. checking to see which reasons earlier close voters have picked).

There's also a bit of extra code for handling the close-as-duplicate subdialog, allowing you to search for potential duplicates and to see which duplicates others have picked, but not to actually select and submit one.

Of course, there's also a conspicuous explanatory message:

Screenshot of disabled close dialog due to bounty

(The freehand arrow in the screenshot is probably redundant. To do: Localize the message into languages other than English.)

In some later version of SOUP, I may consider replacing the current implementation with one that leaves the radio buttons enabled but instead "super-disables" the submit button, since I did actually end up adding such a feature to SOUP for another feature request. But for now, the current implementation seems to work fine. (Any reports of unexpected side effects are, of course, welcome!)

You must log in to answer this question.

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