Last modified: 2009-10-28 06:39:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T23282, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21282 - &unhide=1 on next/prev diff links if already viewing the diff
&unhide=1 on next/prev diff links if already viewing the diff
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Revision deletion (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Aaron Schulz
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-25 16:01 UTC by FT2
Modified: 2009-10-28 06:39 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description FT2 2009-10-25 16:01:50 UTC
On a page that has links for the previous and next edit (or revision), these links should include &unhide=1 if the present page includes &unhide=1.

Effect and significance:

Imagine a page with the following revisions:

Rev #100 (normal)
Rev #101 (normal)
Rev #102 (suppressed)
Rev #103 (suppressed)
Rev #104 (normal)

An oversighter reviewing the activity on this page clicks the DIFF link on revision #101 and is shown the diff between 100/101 as normal. They click "next edit" and are told one of the edits involved (#102) is suppressed. They click "show me" and now see the diff between 101/102. The link for "next edit" to view 102/103 should now include &unhide=1, so they don't get taken away from the revisions to be asked yet again if they want to see the diff. 

In brief, they have asked to see the present diff, and clicked "next edit" on that page; it may be assumed they want to see that diff as well without further question.
Comment 1 FT2 2009-10-25 16:04:08 UTC
Ideally "show me" should be AJAX for speed?
Comment 2 Aaron Schulz 2009-10-28 06:39:57 UTC
Done in r58245

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links