Last modified: 2013-08-26 09:43:55 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 T55299, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53299 - diff=prev of first revision of a page acts funny, claims "No difference"
diff=prev of first revision of a page acts funny, claims "No difference"
Status: NEW
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
1.22.0
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
https://pl.wikipedia.org/w/index.php?...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-24 12:15 UTC by Bartosz Dziewoński
Modified: 2013-08-26 09:43 UTC (History)
5 users (show)

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


Attachments

Description Bartosz Dziewoński 2013-08-24 12:15:58 UTC
diff=prev of first revision of a page acts funny: it claims there is "No difference" between the null and the first version of a page. It acts this way since I458fb688.

Example: https://pl.wikipedia.org/w/index.php?title=Wikipedia:Powiadomienia/Podzi%C4%99kowania&oldid=37320666&diff=prev&uselang=en

It should either show a diff of full page contents against a blank string, or show blank space with no additional message.

Such "diffs" are normally not accessible from the interface, but the Thanks extension can link to them if a user is thanked for such edit.
Comment 1 Umherirrender 2013-08-24 17:07:47 UTC
A diff link between the current version as oldid and diff=next is showing the one version on both side and the "no difference" in the middle, that is also not a behaviour.

The empty string came from a "Short-circuit" where the oldRev is checked against false (and if the revids between old and new the same).

No idea at the moment how to handle this rare case.

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


Navigation
Links