Well, I believe this to be a tad minor.. but still a bug nonetheless.

I recall that sometime today, a new display method for close votes was enabled.. next to the close button, instead of close 1, it now displayed close (1/5), or similar.. The problem comes in voting to close on a question that already has such. It instead comes out to be close (1/5) (2/5); example below:

enter image description here

I suppose I'm wondering if this is indeed a bug, or the intended behavior.. if not, well, here's the report.

  • 15
    Yep, reproduced. I'd say it's a bug.
    – Bart
    Mar 14 '13 at 8:01
  • 4
    Agreed - just came on here to post that. Mar 14 '13 at 8:39
  • Best guess is that it inserted the 2/5 after recieving an update without clearing the original
    – Riking
    Mar 14 '13 at 8:47
  • 6
    Obligatory eeeeeeeek! :D Mar 14 '13 at 8:59
  • 7
    I find your lack of freehand circles disturbing.
    – J. Steen
    Mar 14 '13 at 9:04
  • 2
    @J.Steen better? ;-) Mar 14 '13 at 9:48
  • 1
    @ShaWizDowArd You oscillate the cockles of my heart.
    – J. Steen
    Mar 14 '13 at 9:54
  • @Marc Is this fixed? I still can reproduce it (or by fixed - does it mean next build) Mar 14 '13 at 13:33
  • 2
    @JonClements it will be fixed in the next deploy. If you look in the bottom-right of the page, it says "rev 2013.3.14.856". When it says something else the answer will be "yes" Mar 14 '13 at 13:55
  • @MarcGravell awesome - I'll get ya a pint next time I'm around your area of the woods mate ;) Mar 14 '13 at 14:00
  • @MarcGravell - The issue is not resolved yet. I just voted to close a question and it show me once again. :( Mar 15 '13 at 8:50
  • 2
    @hims056 "When it says something else". It doesn't say something else yet, so the new revision hasn't been deployed yet.
    – J. Steen
    Mar 15 '13 at 9:10
  • @J.Steen - Oh yeh. I extremely need a cup of coffee. Mar 15 '13 at 9:13
  • @hims056 Coffee is very good. I'll have a cup myself, I think. =D
    – J. Steen
    Mar 15 '13 at 9:14

Ah yeah, this sounds a bit familiar. Given that I don't think parentheses ever appear in these links except for in this particular case, that regular expression can probably be genericized to just

a.text().replace(/\s?\([^)]+\)$/, "")

anyway. Barring that,

a.text().replace(/\s?\(\d\/\d\)$/, "")

should work too.

There's also extra whitespace on either side of the text, which makes the links display slightly inconsistently from the other options.

  • 1
    fixed - I went with /\w?\(\d(\/\d)?\)/ to go with the two formats we might expect Mar 14 '13 at 12:27
  • That's fair. I still maintain that \w? should be \s? though, since it seems to want to remove the space it re-adds during the subsequent string concatenation.
    – Tim Stone
    Mar 14 '13 at 12:29
  • 1
    After years of seeing those, regular expressions still look like Orz Nemesis battleship to me. :-P Mar 14 '13 at 12:37
  • 1
    @ShaWizDowArd: Trade-off of power in the expression vs. readability. I think APL is the same.
    – nhahtdh
    Mar 14 '13 at 12:45
  • 2
    Just happened to me a minute ago. Not fixed.
    – j08691
    Mar 14 '13 at 13:37
  • @j08691 not just me then ;) Mar 14 '13 at 13:40
  • @j08691 The fix probably hasn't been deployed yet. I also just saw the problem.
    – andyb
    Mar 14 '13 at 14:50
  • @andyb - the status is marked as completed though.
    – j08691
    Mar 14 '13 at 14:50
  • Completed does not mean deployed. I guess it all depends on what the definition of "complete" is. The defect is fixed in 2013.3.14.856. Current SO version is 2013.3.14.553 so it not deployed to SO yet. It is deployed to meta though (see right column of the footer). If you are still seeing it on meta still then I might agree with you :-)
    – andyb
    Mar 14 '13 at 14:53
  • 6
    I don't like this feature anyway; it makes the spacing all inconsistent. Mar 14 '13 at 17:49

You must log in to answer this question.

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