Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

(Related to Possible bug in locking upvote on an edited question? )

Order of events:

  1. User X answered my question.
  2. Answer sounded reasonable, so I upvoted.
  3. Then I tried to use it, and got a compiler error, so I removed the upvote.
  4. Several minutes later, (>5min, I think) User X edited answer to something else.
  5. I wanted to upvote, but was locked out (can't find the error message to quote here, something like "you can't change your vote until the user edits it")
  6. I couldn't upvote until User X edited the answer again, at my request.

The problem is step #5: The user did edit his answer, after I changed my initial vote. (There is a slight chance that my memory of the order of events is wrong, but I am not sure how to check this.)

The specific Q/A is here: C++: constructor / initializer for array?

share|improve this question
+1 for a reasonable bug, but "no cookie!" for upvoting an answer without testing it – Pops Mar 7 '11 at 17:12
I agree (the "darn, I wish I had tested it before upvoting" thought came to mind), but I also think it's an unreasonably strict standard to test every answer before upvoting. – Jason S Mar 7 '11 at 17:19
up vote 3 down vote accepted

I have checked the data; step 3 occured about 9 minutes after step 4 -- i.e. you removed the upvote after the edit was made. So the behavior was indeed correct.

share|improve this answer
OK, thanks for checking. Darn! I hadn't seen the edited post when I removed the upvote. – Jason S Mar 7 '11 at 17:27

You must log in to answer this question.

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