Last modified: 2010-05-15 16:03:44 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 T15324, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 13324 - strange behavior of revision history page when dir=prev
strange behavior of revision history page when dir=prev
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
1.13.x
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-11 15:08 UTC by Charlotte Webb
Modified: 2010-05-15 16:03 UTC (History)
1 user (show)

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


Attachments

Description Charlotte Webb 2008-03-11 15:08:39 UTC
Go to the history tab of any page with more than 50 edits.

Click on the link titled "Earliest".

url will look similar to: http://en.wikipedia.org/w/index.php?title=Vlade_Divac&dir=prev&action=history

The first row will describe an revision which is obviously not the current one.

However, the "cur" link (to compare it to the most recent version) is missing, and a non-functional [rollback] link appears for users who have that privilege.
Comment 1 Charlotte Webb 2008-03-11 15:17:44 UTC
(In reply to comment #0)
> ...a non-functional [rollback] link...

Actually, it would be functional (and have unexpected results) in a case where, by coincidence, the 50th edit (actually the Nth edit where "action=history&dir=prev&limit=N") and the most recent edit are both made by the same user, as the spurious [rollback] url produced by this bug would be identical to the correct [rollback] url one would use for reverting the "top" edit.
Comment 2 Aaron Schulz 2009-01-06 15:41:19 UTC
Works fine as of now

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


Navigation
Links