Page MenuHomePhabricator

Create user preference to enable unhide=1 by default
Open, Needs TriagePublic

Description

Users with access to revisions, etc. that are hidden by revision deletion must constantly click and reload the page to show and review the deleted content. This is particularly onerous because if the username or edit summary is hidden but the page revision isn't, there is no button that reloads with &unhide=1 in the url; the user must click on the "change visibility" link to get to Special:RevisionDelete, where they can view it. This is inefficient to say the least. This is the case whether a sysop viewing a revisiondeleted page or an oversighter viewing a suppressed page.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 20 2019, 5:16 PM
DoRD added a subscriber: DoRD.Mar 20 2019, 10:37 PM

This is particularly onerous because if the username or edit summary is hidden but the page revision isn't, there is no button that reloads with &unhide=1 in the url;

Wouldn't it make sense to fix this first before going down the route of another user preference...?

Amorymeltzer added a comment.EditedMar 21 2019, 1:11 PM

Wouldn't it make sense to fix this first before going down the route of another user preference...?

That'd certainly be helpful — being able to see the edit summary and/or username in the context of the diff would be great — although I'm not sure where the extra link/button would go without cluttering up the diff interface too much. Moreover, it would still require a click and a page reload. Sysops can deal with this dozens of times a day if reviewing edits (e.g. was this user causing issues or just caught up in another revdel) and oversighters likewise run into this frequently (e.g. which of this user's 10 revdel'd edits are worthy of suppression).

If this features is desired as a user script, it should only take a few minutes

I wrote such a script as https://en.wikipedia.org/wiki/User:LFaraone/autounhide.js , although didn't spend much effort on it and am not experienced in writing MW user scripts.

I wonder if something that required slightly more intentionality would be preferable -- I don't consider myself viewing Wikipedia sites to be particularly sensitive; that is, I generally won't worry about shoulder-surfers accidentally coming into contact with private information without explicit action.

For example, with JS we could make such information visible on mouseover or click. Or add a keyboard shortcut for unhiding.