Currently, once an edit by a user without full edit privilege is suggested, it can be either approved or rejected.
There is a known edge case that cause suggested edits to get auto rejected: (aka edit conflict)
- User with full edit privilege click "edit" and start typing. Let's name this user Joe.
- Since the user from previous step did not yet send the edit, users without full edit privilege can still click the "edit" as well, oblivious to the fact someone else is editing the same post in those very seconds. Such user click "edit" too and start typing. Let's name this user Kenny.
- Kenny is faster than Joe: he send his edit first, creating new suggested edit. Joe is still typing.
- Joe finally done typing. He send his edit to its merry way oblivious to the consequences.
- As result of the full edit made by Joe, Kenny's suggested edit is kicked away and rejected. Boom.
For edge case, it became pretty thick edge. This is not just minor hassle: enough rejections, and the user is banned from suggesting for a whole week: and remember we're talking here about good edits made by good users.
The above used to count for the ban, but no longer do. Thanks Gilles for requesting such a change!
I know it was already suggested to lock edits and similar solutions, but I suggest whole different approach: instead of auto rejecting the suggested edit, dismiss it, i.e. cancel it like it never existed same way a bounty can be revoked by moderator.
In the edit suggestion page it will show "Dismissed" instead of Approved or Rejected maybe with a tooltip explaining what caused this. This will soften the blow from those edge cases, taking the edge out of them. :)