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

TL;DR version: When a long edit suggestion is dismissed, subsequent entries take its place and reviewers loose their position in the list. Essentially, the current view jumps to an arbitrary point further down the page depending on length of the one dismissed.

At present, after casting the final accept/reject vote the entry fades away and is placed in a collapsed list at the top. I have no qualms about that behaviour in general.

However, it can get very disorientating when dealing with long entries that extend beyond the browser view. Subsequent entries take its place (above the visible page) and I end up not knowing where in the list I am. Backtracking to figure out which is the unreviewed entry is harder than it sounds.

Perhaps this mockup can illustrate the problem:

View before and after an edit suggestion is dismissed


I propose that the page be scrolled to the next edit suggestion once the fadeout has completed. Ideally, this is only done if the dismissed entry extends beyond the current view.

I'm aware that some may be opposed to scripts force-scrolling the browser window, but surely its better than having the carpet page being pulled from under your feet.

p.s. This post has some overlap with in this question, but deals with a different problem arrising from the behaviour and proposes a different solution.

p.p.s As mentioned in comments, this also happens in the other /review tabs e.g. when a vote-closed post is minimise. However, the collapsed entry is not moved away and so it serves as a marker which alleviates the confusion.

share|improve this question
The same thing happens with /review/ – NullUserException อ_อ Nov 13 '11 at 1:25
Clever solution. +1 – Matt Dec 19 '11 at 13:55

You must log in to answer this question.

Browse other questions tagged .