Two bugs related to the SO moderator election (noticed wth Firefox 8).
Voting on withdrawn nominations results in showing a message box "Voting is locked for this candidate". The box is hard to read, I think because the arrows and vote counter are transparent, the box is transparent too.
Related to this is the following case, where two withdrawn nominations are displayed next to each other: The message box for the upper nomination is not clickable* - it won't disappear. Voting on the lower one creates a box that does disappear when clicked.
* A small area at the top, that is still inside the container, is still clickable.
Update - As also mentioned in the comments it's caused by the table row's opacity. There's this inline JavaScript that sets the opacity.
<script type="text/javascript">
$(function () { $('#post-8043315').css({ opacity: 0.2 });
$('.withdraw-date').css({ opacity: 1 }); })
</script>
The problem is, that even if the message box would use opacity: 1
, it won't be more opaque than the parent tr
element. I guess .withdraw-date
should be fully opaque too - but is not for the same reason.
Solution? Make only some of the elements transparent. At first glance I say only td.post-signature.owner
, span.vote-up-off
, span.vote-count-post
and span.vote-down-off
should be transparent.
This would also cause the separation line to be visible again, which should be there imho, since the post (even if it was withdrawn) ends and the next one begins.
When the opacity issue is fixed, the upper message box is be closable again.
opacity:1;
for the voting pop up, at least to fix the visual issue. Can't check cause I can't see the withdrawn posts apparently. Edit: actually I did find a post to test and I don't see opacity in the CSS.tr#post-8043315
:element.style { opacity: 0.2; }
"opacity:0.2
. giving theerror-notification
classopacity:1
should fix it. Edit: @PopularDemand now why didn't Chrome's Inspect element tell me that?! I had to look through the HTML.