Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 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

On the Android app, could we have the ability to flag comments we've previously upvoted? This is a fairly regular need for me, and I ran into it again earlier: I flag comments as obsolete when they are, and fairly often, one of them will be a comment I've upvoted.

For an example of a typical case: a comment suggests a great improvement to a question, I upvote it, the author performs that improvement, the comment is now obsolete and (on my PC) I flag it as obsolete. The comments get cleaned up and the question moves on.

There's a request that's been around since 2011 for the site itself: Allow flagging a comment after upvoting it. It's implemented by SOUP (as described here), but the Android app doesn't have a SOUP available to add this functionality to the app for me.

share|improve this question
Per Kasra's comment on this post, I have a feeling this is [status-bydesign] until the behavior changes on the sites without the use of SOUP. – Steven V Jun 23 '14 at 12:41

This was originally declined because the main site, at the time, did not allow flagging an upvoted comment.

However, this is now implemented on the main site: you can flag comments after upvoting them. (But you can't upvote after flagging.) This behaviour is now officially sanctioned, in other words.

In light of this change, I suggest the app should be updated to enable this behaviour.

share|improve this answer
Here's a comment for testing. Make sure your SOUP is disabled (if you have it) so you can be sure it's the main site letting you do this. Upvote this comment, then note you still have the option to flag it. – doppelgreener Sep 23 '14 at 4:11

We talked about this a bit internally, and I think this is going to be . Historically, flagging a comment used to only exist for "This comment is bad or abusive", and while the use case you supply makes perfect sense, I don't think the app should officially sanction being able to flag something after you've already voted on it. If this changes on the site at some point in the future, we'll implement it in the app too.

share|improve this answer
I don't think that feature request can logically be by design. It can be rejected, it can be planned, but not by design. No? – Shadow Wizard Jun 23 '14 at 20:06
@ShadowWizard Touché. – Kasra Rahjerdi Jun 23 '14 at 20:07
Umm... the main site allow this, is there any change of position about the app? – Braiam Sep 23 '14 at 4:40
@KasraRahjerdi The main site has since changed its position on this. Could you re-review? (See my answer.) – doppelgreener Oct 10 '14 at 6:43
@Kasra Ping. You said "If this changes on the site at some point in the future, we'll implement it in the app too." - this has changed on the site, and we've been able to stably flag comments we've also upvoted for about a year now. Could you review the [status-declined] tag on this question, and whether it's still really declined? – doppelgreener Oct 13 '15 at 1:22

You must log in to answer this question.

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