I was attempting to flag a question which is when I came across a strange thing.

I clicked the flag link which opened a Dialog where it asked for options like "very low quality" and "other" radio buttons.

Here first I selected the "very low quality" radio button and after a while, I thought I should go for the "other" radio button.

So I clicked on it, and thought of entering some content. But again I changed my mind and went to "very low quality" radio button. I clicked it and now the "flag question" button was still disabled.

Can anyone tell me why this has happened?

enter image description here

  • Can't reproduce this, works for me. – Joachim Sauer Jul 26 '11 at 12:16
  • select other, click inside the edit column, without typing anything again select "very low quality". the button will be disabled. This is how I got it. – Andro Selva Jul 26 '11 at 12:18
  • 3
    Repro with FF6 Beta. Clicking the RadioButton shortly does reactivate and instantly deactivate the button again. Holding the click for half a second does reactivate the button. – Time Traveling Bobby Jul 26 '11 at 12:19
  • oh fine. But I believe that there will be someone like me who might not know this. – Andro Selva Jul 26 '11 at 12:20
  • 5
    Reproduced. Click back and forth between very low quality and other. Fill in some text in the other dialog. Then click very low quality, and the Flag Question button will be disabled. – Awesome Poodles Jul 26 '11 at 12:21
  • 1
    Oh. Weird. I managed to reproduce this at one point, but not any other point. Following @Bobby's comment, it seems to be some measure of haste involved, but I can't reliably reproduce it. IE8/XP here. What I have noticed, though, is that if you do get the button disabled, then clicking the "very low quality" radio a second time will usually fix it. – Grace Note Jul 26 '11 at 12:21
  • 2
    Repro in Chrome using the info from @Bobby: clicking it shortly triggers the bug. Strange. – Joachim Sauer Jul 26 '11 at 12:21
  • @Grace Note Could you please follow my previous comment and try? – Andro Selva Jul 26 '11 at 12:22
  • 2
    My guess: the unblur event of the text field checks for sufficient length of the comment and the onfocus of the radio button enables the button. A timing difference causes the unblur to be handled after the onfocus if the click doesn't take long. Therefore, the button is re-enabled and re-disabled in quick succession. – Joachim Sauer Jul 26 '11 at 12:23
  • Trying your original comment did not work, that was my initial test that did not reproduce (and was my original comment noting such). – Grace Note Jul 26 '11 at 12:23
  • You really have to work at this to see the problem. And anyway, clicking the radio button again solves it. – Cody Gray Jul 26 '11 at 12:23
  • @Grace Note Well, I am using Mozilla. I am not sure about other browsers though! – Andro Selva Jul 26 '11 at 12:24
  • @GraceNote -- i repro'd it in Chrome 12 Windows 7 – Naftali aka Neal Jul 26 '11 at 14:10

A fix for this will be pushed tonight.

|improve this answer|||||
  • couldn't see any fix yet – Andro Selva Aug 24 '11 at 12:18
  • You're still seeing the issue? What browser are you using? – Jarrod Dixon Aug 24 '11 at 13:38
  • We've had a few issues lately with our CDN - try clearing your cache and getting the latest javascript. – Jarrod Dixon Aug 24 '11 at 13:58
  • @JarrodDixon - I think it's been long enough that we can no longer blame this on the CDN or caching. Still seeing it with Chrome 19.latest, as are others: Flag button gets perma-disabled – Kevin Vermeer May 23 '12 at 13:45

You must log in to answer this question.

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