I often click on the score to see the up/down votes only to find the score represents the actual votes.

Such as
Score shows 10, clicking reveals 10 upvotes and 0 downvotes.
Score shows -7, clicking reveals 7 downvotes 0 upvotes.

So what about highlighting the score when there are both up and downvotes?
So we know whether to click or not.

For example, when there are upvotes AND downvotes, the score is underlined, or circled, or a little "+/-" next to the score, etc - I'm not suggesting these exact things, they're just ideas so you know what I'm talking about.

"0" score:
If no votes, then don't highlight, as the score represents all votes (none, 0 votes 0 score).
If score is 0 from net calc from up and downvotes, then highlight it.


Obviously this would only apply to those with the privilege to see votes (1K rep).

It's not an essential feature, but would be quite useful.

It could save us a lot of clicking, and possibly be beneficial to site resources (if this feature uses less than currently clicking does).


Alternatively, we could highlight the score when there are only up "OR" down votes. However I think it would be better to highlight it when there is something additional to see.
Highlighting to state "nothing to see here" is a bit less logical, imo.

  • Just to explain my downvote - adding extra code to do this seems to be a bad use of devs time. If you want to know the votes just click (as you have said) - there are only a few times when I would ever want to know (and I'd imagine others may be the same) and when I do - I just click. It's not intrusive or high effort. – Ro-Reinstate Monic-Alsop May 15 '15 at 7:35
  • @RoryAlsop No probs. As I said, it's not essential, just useful. Clicking Q & A scores invokes a DB query (hence 1 sec limit per click). Stack Overflow has 25 million Q/As, 4.3 million users - lots of potential DB queries. This feature is not to resolve/ease that, it's just a possibly beneficial side effect. meta.stackexchange.com/a/1007/230506 - so might be a useful use of dev time :) (Only Stack would know this, and this feature might be more resource hungry or negligible difference). Also, I know it's not "high effort", but that's no reason to not introduce something useful ;) – James May 15 '15 at 14:31

You must log in to answer this question.

Browse other questions tagged .