1. Go to any random heavily downvoted answer
  2. Click on the flag button
  3. . Profit!!!

Is this ?

This is still happening, over a year later, and with work having been done updating the flagging options.

  • The FHC countdown time is running... Feb 21, 2010 at 1:53
  • In addition, the flag popup on heavily downvoted questions is not gray, supporting John Rudy's post. I just saw this behavior myself a few minutes ago.
    – Pops
    Dec 9, 2010 at 15:54
  • 1
    This is still occurring in Review as evidenced in meta.stackexchange.com/questions/97472/…
    – jonsca
    Aug 22, 2011 at 9:30
  • I had a thought as to how the situation could be alleviated during Review times -- if there were a setting with which we could turn off favorites/ignored tags feature just for the Review stream, this would be less of a problem.
    – jonsca
    Aug 27, 2011 at 9:43
  • @jonsca Agreed, having questions grayed out in review is pointless.
    – fredley
    Oct 12, 2011 at 13:19
  • There are quite a few highly downvoted answers on which to test this behavior here. Alternatively, search for [status-declined] votes:100. Oct 12, 2011 at 13:30

5 Answers 5


Bumping this question, because the problem is still present. I think it is actually a problematic bug -- I initially thought that the flagging dialogue was disabled for some reason (e.g. because the answer had already been deleted).

Flag dialogue box  faded

I can't believe this would be difficult to fix -- something like this would correct it, I think:

.popup {
    color: #000;
  • I dislike that proposed fix, it means we would have to maintain another rule per site
    – waffles
    Nov 2, 2011 at 2:20

Was about to bug report this as well. Only my example had a narwhal. enter image description here

  • 2
    I wish mine had a narwhal.
    – Pollyanna
    May 31, 2011 at 15:17
  • 6
    That's either a pearl necklace or some serious overbite
    – random
    May 31, 2011 at 15:19
  • @AdamDavis: Throw me a link and I'll narwhalify it.
    – user1228
    May 31, 2011 at 15:20
  • 7
    For the unbelievers: A Narwhal is the obvious crossbreed between a meremaid and a unicorn. Narwals do exist, so both meremaids and unicorns must exist. Jun 7, 2011 at 11:32
  • They are not overbites; they are love bites. (I guess the narwhal has a fiancè.)
    – apaderno
    Sep 8, 2011 at 3:09
  • Wait, how did you get 7 downvotes and an accept in 38 seconds?!?
    – John
    Oct 12, 2011 at 17:06
  • this should also be fixed
    – waffles
    Nov 2, 2011 at 2:19
  • @Will has a net vote of -7, yet is still accepted. Cool. :) Nov 2, 2011 at 5:45
  • 1
    @Gamecat You are a cross between a game and a cat, and you exist. Therefore, all of the following creatures must exist: the horse [and his boy], the unicorn, the mermaid, and the walrus-game-cat-waffle. This is the reason I have 2+k rep on SO: my superior logic and inability to post completely tangential, sporadic, numerous, heavily edited, or wordy comments containing several references, none of which I expect to be picked up, and hard to parse sentences composed of infallible grammar. And also... I forgot. [Whatever I forgot. I forgot what I forgot. Otherwise, I wouldn't have forgotten it!!] Nov 2, 2011 at 5:53
  • (Sorry @Won'tಠ_ಠ for the last comment. :) On another side note, it used up exactly all the characters allotted for a comment.) Nov 2, 2011 at 5:53

We were setting "color" on the top level post div, the flag was inheriting it. I changed it so we target .downvoted-answer .post-text

I just change a bunch of style sheets. This should be resloved.

Another bug was lurking ... on many SE 2.0 sites the downvoted styling was overridden. That is also fixed.

If every single stylesheet on all our sites breaks ... it is my fault

  • to be deployed later
    – waffles
    Nov 2, 2011 at 2:21

Based on the Web Developer Toolbar in Firefox, it appears that the Flag Reasons box is a child element of the <td> which contains the post. As a result, although the style information piece in the toolbar wasn't picking up font colors at all for me, I'm going to guess that the Flag Reasons box inherits its font color from the post itself, so if the post font color changes, so does it. And of course, the post font color does in fact change when the post is heavily downvoted.

Whether or not that's "correct" behavior is debatable, but that's how it appears to be happening.

  • I figured so much, and I'm reporting it as I imagine that behavior to be more likely to be the result of somebody forgetting a special case in the CSS than a specific design decision for a specific rare situation.
    – perbert
    Feb 21, 2010 at 2:47

I'm getting this too. It can be annoying, as if another transparent entry falls on top of a button in the dialog, I can't click it.

No Narwhal

  • 1
    This is not the same problem. Oct 12, 2011 at 12:02
  • @KevinVermeer Oh, I initially opened this as a new question, but was informed it was a dupe.
    – fredley
    Oct 12, 2011 at 12:22
  • 3
    It is the same problem, the dialog inherits the style properties of the post. Although the fact that you can't click some of the options is likely a separate issue. I'm not sure off-hand why that would happen here...hmm.
    – Tim Stone
    Oct 12, 2011 at 12:24
  • Whoops! I saw black text and transparency, and assumed that it was different from the gray text and opacity. You're right, it's the same problem. Oct 12, 2011 at 13:16
  • @TimStone You can see on the example posted that How to avoid using membership provider? is on top of the dialog, and I wouldn't be able to flag this as spam as a result (I'd have to close the dialog, scroll, and reopen it).
    – fredley
    Oct 13, 2011 at 8:21

You must log in to answer this question.

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