5

In the old comment flagging UI (the one before major changes were made to the comment flagging system recently), it used to be that if another comment was flagged within the last five seconds, the submit button would be disabled, and only re-enable itself once the rate limit expired.

However, with the new flagging UI, this feature appears to have been removed: the button is always enabled, and clicking it before the rate limit expires produces an error message.

Can this feature please be added back? I liked that feature because I often flag multiple comments at a time, and the current error message covers up the button, meaning it has to be closed before I can re-click it.

  • This is the comment flagging UI that appears on post pages and was updated last August with the CoC rollout? I'm looking at the old code and I don't see the behavior you're describing. When you opened the old popup, Submit would be disabled until you picked an option, but there was no timer or logic around the rate limit. Is it possible a user script was providing this behavior? – Brian Nickel May 22 at 4:39
  • Code around the rate limit would probably be tricky to implement and the UX would be nuanced, but we could do something about that error message by porting it to a Stacks-based error toast. That'll at least keep it out from under your cursor. – Brian Nickel May 22 at 4:42
  • @BrianNickel I think the SOUP script was providing that feature; can you please check the old code again and see if it works with that script enabled? – Sonic the Anonymous WizHog May 22 at 6:33
  • Yep, the code is at github.com/vyznev/soup/blob/… Same could probably be applied to the new dialog by tweaking the selectors. – Brian Nickel May 27 at 3:50

You must log in to answer this question.

Browse other questions tagged .