Take the 2-minute tour ×
Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. It's 100% free, no registration required.

The Sales Pitch

enter image description here

This userscript enhances the suggested edit queue to remove the usability annoyances we all know and love hate.

Added bonus:

  • Suggested Edits which have already been voted on by another user are automatically listed first
  • Auto-updater built in, so you'll get new features automatically
  • Individual features can be toggled on and off via preferences shown at the bottom of the edit queue.

Install

Click here to download and install

Source Code

The source code is available on Github. Fork, submit issues and add pull requests as much as you want.

Released under the MIT license, so do whatever you want with it.

Roadmap

  1. Allow clearing of Ignored edits

Contact

Created by me, Matt Lunn. Contact me via contact@mattlunn.me.uk (although I can't see why you'd want do ;)).

share|improve this question
    
This is awesome! Can you make it so the improve button works without navigating away too, or alternatively can be middle clicked like a link rather than a button to open in a new tab. (I.e. straight to the edit page rather than via the permalink) –  Flexo Jun 16 '12 at 17:39
    
Any chance you could make the "ignore" button the 4th one rather than the first one? It turns out I've learned the position of the buttons rather well and I've twice hit approve when I meant to reject. –  Flexo Jun 17 '12 at 16:44
    
@Flexo: It looks like the SE Engine doesn't support inline editing of suggested edits, but I'll look at middle-clicking the improve option! –  Matt Jun 20 '12 at 12:33
    
@Flexo: Mmm, might need more convincing on that one... I've got used to it on the left now ;)... when I originally added it, it was 4th, but in my head I had named the fields from the right, not the left so had the apposite annoyance to what you're experiencing... –  Matt Jun 20 '12 at 12:34
    
I can't say I'm enamored with the new beta interface. Sadly, the most important part of your script (moving edits to the top once you've acted on them) stopped working (Chrome 20) about the time /review-beta was introduced. Is there any chance to make it work again? –  Gilles Jul 26 '12 at 22:43
add comment

1 Answer

THANK YOU

Thank you, thank you, thank you! Having a consistent response to validating an edit, and not seeing the edits I've already reviewed over and over, makes reviewing suggested edits so much less painful.


There's a quoting bug when a title contains characters that are active in HTML is moved to the top. This is how Executing elements inserted with .innerHTML appears after I've acted on it:

collapsed title

share|improve this answer
    
@Gilles: This should now be fixed in the userscript version. If you un-install the Chrome Extension and then click the install link in the post again, you should get your hands on an auto-updating userscript (with the bug fixed). –  Matt Jun 13 '12 at 10:15
    
@Matt Thanks, I confirm the fix. –  Gilles Jun 13 '12 at 13:21
    
Out of interest, have you got the latest version or not? –  Matt Jun 13 '12 at 13:23
    
@Matt Check your inbox :) I have a version with the fade option. Appears as version 2.0.0. –  Gilles Jun 13 '12 at 13:25
    
@Matt New minor bug report: under “add to the top”, edits on tag wiki lose the name of the tag when they're acted on. –  Gilles Jun 15 '12 at 23:20
    
This was status-by-design when I wrote it, but I've added that functionality in the latest (released) version. –  Matt Jun 16 '12 at 15:17
    
@Matt Thanks. Now up: title quoting bug, it looks like you need to add something to escape characters in the title. –  Gilles Jun 21 '12 at 20:19
    
@Gilles: Fixed, thanks :) –  Matt Jun 21 '12 at 21:00
add comment

You must log in to answer this question.

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